Notebookcheck Logo

AMD A10-5757M vs AMD A6-5357M vs AMD A8-5557M

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.

AMD A6-5357M

► remove from comparison AMD A6-5357M

The AMD A6-5357M is a mobile dual-core processor based on the Richland-architecture. In contrast to the A6-5350M, the A6-5357M is a BGA version. As successor to the A6-4400M, the A6-5350M/5357M has a slightly higher CPU and graphics performance and settles in the low end segment. The APU integrates 2 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 module 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.9 to 3.5 GHz, the A6-5357M should perform about 15 percent faster than the A6-4400M and just reach a Pentium P6100. Consequently, the performance in less demanding applications and games is sufficient.

The graphics unit called Radeon HD 8450G offers 192 shader units (VLIW4) and clocks slightly higher than the HD 7520G at 533 - 720 MHz. With fast dual-channel memory, performance is expected to match a dedicated Radeon HD 7470M.

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 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.

ModelAMD A10-5757MAMD A6-5357MAMD A8-5557M
SeriesAMD A-SeriesAMD A-SeriesAMD A-Series
CodenameRichlandRichlandRichland
Series: A-Series Richland
AMD A10-5750M2.5 - 3.5 GHz4 / 4
» AMD A10-5757M2.5 - 3.5 GHz4 / 4
AMD A10-5745M2.1 - 2.9 GHz4 / 4
AMD A8-5550M2.1 - 3.1 GHz4 / 4
AMD A8-5557M2.1 - 3.1 GHz4 / 4
AMD A8-5545M1.7 - 2.7 GHz4 / 4
AMD A6-5350M2.9 - 3.5 GHz2 / 2
AMD A6-5357M2.9 - 3.5 GHz2 / 2
AMD A4-5150M2.7 - 3.3 GHz2 / 2
AMD A6-5345M2.2 - 2.8 GHz2 / 2
AMD A4-5145M2 - 2.6 GHz2 / 2
AMD A10-5750M2.5 - 3.5 GHz4 / 4
AMD A10-5757M2.5 - 3.5 GHz4 / 4
AMD A10-5745M2.1 - 2.9 GHz4 / 4
AMD A8-5550M2.1 - 3.1 GHz4 / 4
AMD A8-5557M2.1 - 3.1 GHz4 / 4
AMD A8-5545M1.7 - 2.7 GHz4 / 4
AMD A6-5350M2.9 - 3.5 GHz2 / 2
» AMD A6-5357M2.9 - 3.5 GHz2 / 2
AMD A4-5150M2.7 - 3.3 GHz2 / 2
AMD A6-5345M2.2 - 2.8 GHz2 / 2
AMD A4-5145M2 - 2.6 GHz2 / 2
AMD A10-5750M2.5 - 3.5 GHz4 / 4
AMD A10-5757M2.5 - 3.5 GHz4 / 4
AMD A10-5745M2.1 - 2.9 GHz4 / 4
AMD A8-5550M2.1 - 3.1 GHz4 / 4
» AMD A8-5557M2.1 - 3.1 GHz4 / 4
AMD A8-5545M1.7 - 2.7 GHz4 / 4
AMD A6-5350M2.9 - 3.5 GHz2 / 2
AMD A6-5357M2.9 - 3.5 GHz2 / 2
AMD A4-5150M2.7 - 3.3 GHz2 / 2
AMD A6-5345M2.2 - 2.8 GHz2 / 2
AMD A4-5145M2 - 2.6 GHz2 / 2
Clock2500 - 3500 MHz2900 - 3500 MHz2100 - 3100 MHz
L2 Cache4 MB1 MB4 MB
Cores / Threads4 / 42 / 24 / 4
TDP35 Watt35 Watt35 Watt
Technology32 nm32 nm32 nm
SocketBGABGABGA
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 ControllerSSE (1, 2, 3, 3S, 4.1, 4.2, 4A), x86-64, AES, AVX, FMA, DDR3-1600 Controller
iGPUAMD Radeon HD 8650G (600 - 720 MHz)AMD Radeon HD 8450G (533 - 720 MHz)AMD Radeon HD 8550G (554 - 720 MHz)
Architecturex86x86x86
Announced

Benchmarks

Cinebench R11.5 - Cinebench R11.5 CPU Multi 64 Bit
min: 2.14     avg: 2.2     median: 2.2 (4%)     max: 2.31 Points
1.9 Points (4%)
Cinebench R11.5 - Cinebench R11.5 CPU Single 64 Bit
min: 0.87     avg: 0.9     median: 0.9 (3%)     max: 0.89 Points
0.8 Points (2%)
Cinebench R10 - Cinebench R10 Rend. Single (32bit)
2182 Points (19%)
2115 Points (19%)
Cinebench R10 - Cinebench R10 Rend. Multi (32bit)
3774 Points (5%)
5259 Points (7%)
Cinebench R10 - Cinebench R10 Rend. Multi (64bit)
8232 Points (7%)
7373 Points (7%)
Cinebench R10 - Cinebench R10 Rend. Single (64bit)
3247 Points (20%)
2871 Points (18%)
wPrime 2.10 - wPrime 2.0 1024m *
901 s (11%)
903 s (11%)
wPrime 2.10 - wPrime 2.0 32m *
28.7 s (6%)
26.8 s (5%)
WinRAR - WinRAR 4.0
1266 Points (7%)
1860 Points (11%)
X264 HD Benchmark 4.0 - x264 Pass 2
7.6 fps (3%)
12.4 fps (6%)
X264 HD Benchmark 4.0 - x264 Pass 1
39.2 fps (11%)
62.5 fps (17%)
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
2986 Points (6%)
2747 Points (6%)
Super Pi mod 1.5 XS 1M - Super Pi mod 1.5 XS 1M *
39 s (8%)
31.6 s (7%)
Super Pi mod 1.5 XS 2M - Super Pi mod 1.5 XS 2M *
86 s (4%)
71.9 s (3%)
Super Pi Mod 1.5 XS 32M - Super Pi mod 1.5 XS 32M *
2237 s (10%)
1884 s (8%)
SiSoft Sandra Dhrystone (MIPS) - SiSoft Sandra Dhrystone (MIPS)
33372 MIPS (16%)
29520 MIPS (14%)
SiSoft Sandra Whetstone (MFLOPS) - SiSoft Sandra Whetstone (MFLOPS)
22906 MFLOPS (18%)
21160 MFLOPS (16%)
3DMark Vantage - 3DM Vant. Perf. CPU no Physx
6493 Points (7%)
6116 Points (6%)
3DMark 11 - 3DM11 Performance Physics
min: 2533     avg: 2709     median: 2772 (10%)     max: 2823 Points
2318 Points (8%)
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 3 - Geekbench 3 32 Bit Multi-Core
3498 Points (6%)
Geekbench 3 - Geekbench 3 32 Bit Single-Core
1591 Points (31%)
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%)

Average Benchmarks AMD A10-5757M → NAN% n=

Average Benchmarks AMD A8-5557M → NAN% n=

- 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

v1.17
log 11. 08:19:03

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

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

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

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

#4 did not recreate cache, as it is less than 5 days old! Created at Sat, 06 Aug 2022 13:13:32 +0200 +0s ... 0s

#5 linkCache_getLink no uid found +0.008s ... 0.009s

#6 linkCache_getLink no uid found +0.008s ... 0.016s

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

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

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

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

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

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

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

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

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

#16 linkCache_getLink no uid found +0.005s ... 0.021s

#17 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.021s

#18 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.021s

#19 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.021s

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

#21 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.021s

#22 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.021s

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

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

#25 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.021s

#26 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.021s

#27 composed specs +0s ... 0.021s

#28 did output specs +0s ... 0.021s

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

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

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

#32 got single benchmarks 3747 +0.007s ... 0.029s

#33 getting avg benchmarks for device 4157 +0s ... 0.03s

#34 got single benchmarks 4157 +0s ... 0.03s

#35 getting avg benchmarks for device 4156 +0s ... 0.03s

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

#37 got single benchmarks 4156 +0.007s ... 0.037s

#38 got avg benchmarks for devices +0s ... 0.037s

#39 linkCache_getLink no uid found +0s ... 0.038s

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

#41 linkCache_getLink no uid found +0s ... 0.038s

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

#71 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.048s

#72 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.049s

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

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

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

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

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

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

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

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

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

#82 linkCache_getLink no uid found +0s ... 0.052s

#83 linkCache_getLink no uid found +0s ... 0.052s

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

#85 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.052s

#86 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.053s

#87 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.053s

#88 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.054s

#89 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.054s

#90 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.055s

#91 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.055s

#92 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.056s

#93 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.056s

#94 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.056s

#95 min, max, avg, median took s +0s ... 0.057s

#96 return log +0s ... 0.057s

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)