Notebookcheck Logo
, , , , , ,
search relation.
, , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ,
 

AMD A8-5557M vs AMD A10-5757M

AMD A8-5557M

► remove from comparison AMD A8-5557M

The AMD A8-5557M is a mobile quad-core processor based on the Richland-architecture. In contrast to the A8-5550M, the 5557M is a BGA version. As successor to the A8-4500M, the A8-5550M/5557M has a slightly higher CPU and graphics performance and settles in the lower middle class. The APU integrates 4 CPU cores, a DirectX 11 graphics unit and the Northbridge along with a DDR3 memory controller.

Compared to Trinity, Richland has been modified just slightly. Therefore, no changes in the feature set or the Pro-MHz performance can be reported. The design of the chip is still based on the Bulldozer architecture, which consists of so-called modules. Each of the two modules integrates 2 integer units, but only one FPU. Just like Trinity, Richland supports nearly all current techniques such as AVX (including FMA), AES or Turbo Core.

According to the clock rates of 2.1 to 3.1 GHz, the A8-5557M should perform about 15 percent slower than the A10-5750M and just reach a Core i3-2310M. Consequently, the performance in current applications and games is sufficient.

The graphics unit called Radeon HD 8550G offers 256 shader units (VLIW4) and clocks slightly higher than the HD 7640G at 554 -  720 MHz. With fast dual-channel memory, performance is expected to match a dedicated Radeon HD 7570M.

The power consumption of the entire APU is rated at 35 watts, which is comparable to conventional middle-class models of competition. Thus, the APU is best suited for 14 inch notebooks or bigger.

AMD A10-5757M

► remove from comparison AMD A10-5757M

The AMD A10-5757M is a mobile quad-core processor based on the Richland-architecture. In contrast to the A10-5750M, the 5757M is a BGA version. As the successor of the A10-4600M, the A10-5750M/5757M offers a slightly higher CPU and graphics performance and represents the new top model of the A-series (March 2013).

Compared to Trinity, Richland has been modified just slightly. Therefore, no changes in the feature set or the Pro-MHz performance can be reported. The design of the chip is still based on the Bulldozer architecture, which consists of so-called modules. Each of the two modules integrates 2 integer units, but only one FPU. Just like Trinity, Richland supports nearly all current techniques such as AVX (including FMA), AES or Turbo Core.

Our benchmarks show a performance increase of around 10 percent on the A10-4600M. Thus, the A10-5757M performs at the level of a Core i3-2330M (Sandy Bridge).

The graphics unit called Radeon HD 8650G offers 384 shader units (VLIW4) and clocks at 533 - 720 MHz (slightly higher than the HD 7660G). With fast dual-channel memory, performance is similar to a dedicated HD 7670M.

The power consumption of the entire APU is rated at 35 watts, which is comparable to conventional middle-class models of competition. Thus, the APU is best suited for 14 inch notebooks or bigger.

ModelAMD A8-5557MAMD A10-5757M
SeriesAMD A-SeriesAMD A-Series
CodenameRichlandRichland
Series: A-Series Richland
AMD A10-5750M compare2.5 - 3.5 GHz4 / 4
AMD A10-5757M2.5 - 3.5 GHz4 / 4
AMD A10-5745M compare2.1 - 2.9 GHz4 / 4
AMD A8-5550M compare2.1 - 3.1 GHz4 / 4
» AMD A8-5557M2.1 - 3.1 GHz4 / 4
AMD A8-5545M compare1.7 - 2.7 GHz4 / 4
AMD A6-5350M compare2.9 - 3.5 GHz2 / 2
AMD A6-5357M compare2.9 - 3.5 GHz2 / 2
AMD A4-5150M compare2.7 - 3.3 GHz2 / 2
AMD A6-5345M compare2.2 - 2.8 GHz2 / 2
AMD A4-5145M compare2 - 2.6 GHz2 / 2
AMD A10-5750M compare2.5 - 3.5 GHz4 / 4
» AMD A10-5757M2.5 - 3.5 GHz4 / 4
AMD A10-5745M compare2.1 - 2.9 GHz4 / 4
AMD A8-5550M compare2.1 - 3.1 GHz4 / 4
AMD A8-5557M2.1 - 3.1 GHz4 / 4
AMD A8-5545M compare1.7 - 2.7 GHz4 / 4
AMD A6-5350M compare2.9 - 3.5 GHz2 / 2
AMD A6-5357M compare2.9 - 3.5 GHz2 / 2
AMD A4-5150M compare2.7 - 3.3 GHz2 / 2
AMD A6-5345M compare2.2 - 2.8 GHz2 / 2
AMD A4-5145M compare2 - 2.6 GHz2 / 2
Clock2100 - 3100 MHz2500 - 3500 MHz
L2 Cache4 MB4 MB
Cores / Threads4 / 44 / 4
TDP35 Watt35 Watt
Technology32 nm32 nm
SocketBGABGA
FeaturesSSE (1, 2, 3, 3S, 4.1, 4.2, 4A), x86-64, AES, AVX, FMA, DDR3-1600 ControllerSSE (1, 2, 3, 3S, 4.1, 4.2, 4A), x86-64, AES, AVX, FMA, DDR3-1600 Controller
iGPUAMD Radeon HD 8550G (554 - 720 MHz)AMD Radeon HD 8650G (600 - 720 MHz)
Architecturex86x86
Announced

Benchmarks

Cinebench R11.5 - Cinebench R11.5 CPU Multi 64 Bit
1.9 Points (4%)
min: 2.14     avg: 2.2     median: 2.2 (4%)     max: 2.31 Points
Cinebench R11.5 - Cinebench R11.5 CPU Single 64 Bit
0.8 Points (22%)
min: 0.87     avg: 0.9     median: 0.9 (25%)     max: 0.89 Points
Cinebench R10 - Cinebench R10 Rend. Single (32bit)
2115 Points (19%)
2182 Points (19%)
Cinebench R10 - Cinebench R10 Rend. Multi (32bit)
5259 Points (7%)
3774 Points (5%)
Cinebench R10 - Cinebench R10 Rend. Multi (64bit)
7373 Points (7%)
8232 Points (7%)
Cinebench R10 - Cinebench R10 Rend. Single (64bit)
2871 Points (18%)
3247 Points (20%)
wPrime 2.10 - wPrime 2.0 1024m *
903 s (11%)
901 s (11%)
wPrime 2.10 - wPrime 2.0 32m *
26.8 s (5%)
28.7 s (6%)
WinRAR - WinRAR 4.0
1860 Points (11%)
1266 Points (7%)
X264 HD Benchmark 4.0 - x264 Pass 2
12.4 fps (6%)
7.6 fps (3%)
X264 HD Benchmark 4.0 - x264 Pass 1
62.5 fps (17%)
39.2 fps (11%)
TrueCrypt - TrueCrypt Serpent
0.1 GB/s (4%)
0.1 GB/s (4%)
TrueCrypt - TrueCrypt Twofish
0.2 GB/s (5%)
0.2 GB/s (5%)
TrueCrypt - TrueCrypt AES
1.1 GB/s (4%)
1.1 GB/s (4%)
3DMark 06 - CPU - 3DMark 06 - CPU
2747 Points (6%)
2986 Points (6%)
Super Pi mod 1.5 XS 1M - Super Pi mod 1.5 XS 1M *
31.6 s (7%)
39 s (8%)
Super Pi mod 1.5 XS 2M - Super Pi mod 1.5 XS 2M *
71.9 s (3%)
86 s (4%)
Super Pi Mod 1.5 XS 32M - Super Pi mod 1.5 XS 32M *
1884 s (8%)
2237 s (10%)
SiSoft Sandra Dhrystone (MIPS) - SiSoft Sandra Dhrystone (MIPS)
29520 MIPS (14%)
33372 MIPS (16%)
SiSoft Sandra Whetstone (MFLOPS) - SiSoft Sandra Whetstone (MFLOPS)
21160 MFLOPS (16%)
22906 MFLOPS (18%)
3DMark Vantage - 3DM Vant. Perf. CPU no Physx
6116 Points (6%)
6493 Points (7%)
3DMark 11 - 3DM11 Performance Physics
2318 Points (8%)
min: 2533     avg: 2709     median: 2772 (10%)     max: 2823 Points
3DMark - 3DMark Ice Storm Physics
21396 Points (14%)
3DMark - 3DMark Cloud Gate Physics
1760 Points (4%)
3DMark - 3DMark Fire Strike Standard Physics
2441 Points (6%)
Geekbench 2 - 32 Bit - Geekbench Stream
3331 Points (27%)
Geekbench 2 - 32 Bit - Geekbench Memory
2913 Points (26%)
Geekbench 2 - 32 Bit - Geekbench Floating Point
5444 Points (11%)
Geekbench 2 - 32 Bit - Geekbench Integer
4222 Points (8%)
Geekbench 2 - 32 Bit - Geekbench Total Score
4298 Points (11%)
Geekbench 3 - Geekbench 3 32 Bit Multi-Core
3498 Points (6%)
Geekbench 3 - Geekbench 3 32 Bit Single-Core
1591 Points (33%)

Average Benchmarks AMD A8-5557M → 100% n=22

Average Benchmarks AMD A10-5757M → 99% n=22

- Range of benchmark values for this graphics card
- Average benchmark values for this graphics card
* Smaller numbers mean a higher performance
1 This benchmark is not used for the average calculation

Add one or more devices and compare

In the following list you can select (and also search for) devices that should be added to the comparison. You can select more than one device.

restrict list:

show all (including archived), 2022, 2021
v1.17
log 28. 02:53:24

#0 checking url part for id 4156 +0s ... 0s

#1 checking url part for id 3747 +0s ... 0s

#2 not redirecting to Ajax server +0s ... 0s

#3 did not recreate cache, as it is less than 5 days old! Created at Mon, 23 May 2022 13:12:29 +0200 +0s ... 0s

#4 linkCache_getLink no uid found +0.007s ... 0.007s

#5 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.008s

#6 linkCache_getLink no uid found +0.005s ... 0.013s

#7 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.013s

#8 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.013s

#9 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.013s

#10 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.013s

#11 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.013s

#12 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.013s

#13 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.013s

#14 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.013s

#15 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.013s

#16 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.013s

#17 composed specs +0s ... 0.013s

#18 did output specs +0s ... 0.013s

#19 getting avg benchmarks for device 4156 +0s ... 0.014s

#20 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.014s

#21 got single benchmarks 4156 +0.007s ... 0.021s

#22 getting avg benchmarks for device 3747 +0s ... 0.021s

#23 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.022s

#24 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.022s

#25 got single benchmarks 3747 +0.007s ... 0.028s

#26 got avg benchmarks for devices +0s ... 0.028s

#27 linkCache_getLink no uid found +0.001s ... 0.029s

#28 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.029s

#29 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.03s

#30 linkCache_getLink no uid found +0s ... 0.03s

#31 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.03s

#32 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.03s

#33 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.031s

#34 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.031s

#35 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.031s

#36 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.031s

#37 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.032s

#38 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.032s

#39 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.032s

#40 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.032s

#41 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.033s

#42 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.033s

#43 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.033s

#44 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.034s

#45 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.034s

#46 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.034s

#47 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.034s

#48 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.035s

#49 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.035s

#50 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.035s

#51 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.036s

#52 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.036s

#53 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.036s

#54 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.037s

#55 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.037s

#56 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.037s

#57 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.038s

#58 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.038s

#59 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.039s

#60 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.039s

#61 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.04s

#62 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.04s

#63 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.04s

#64 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.04s

#65 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.041s

#66 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.041s

#67 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.041s

#68 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.042s

#69 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.042s

#70 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.042s

#71 linkCache_getLink no uid found +0s ... 0.042s

#72 linkCache_getLink no uid found +0s ... 0.042s

#73 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.042s

#74 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.043s

#75 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.043s

#76 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.044s

#77 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.044s

#78 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.044s

#79 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.045s

#80 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.045s

#81 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.045s

#82 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.046s

#83 min, max, avg, median took s +0s ... 0.046s

#84 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.046s

#85 return log +0.004s ... 0.05s

Please share our article, every link counts!
> Notebook / Laptop Reviews and News > Benchmarks / Tech > Processor Comparison - Head 2 Head
Redaktion, 2017-09- 8 (Update: 2017-09-11)