Notebookcheck Logo

AMD A10-5757M vs AMD A6-5350M vs AMD A6-5357M

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-5350M

► remove from comparison AMD A6-5350M

The AMD A6-5350M is a mobile dual-core processor based on the Richland-architecture. As successor to the A6-4400M, the A6-5350M 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-5350M performs about 15 percent faster than the A6-4400M and just reaches 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. With fast dual-channel memory, performance matches 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 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.

ModelAMD A10-5757MAMD A6-5350MAMD A6-5357M
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 MHz2900 - 3500 MHz
L2 Cache4 MB1 MB1 MB
Cores / Threads4 / 42 / 22 / 2
TDP35 Watt35 Watt35 Watt
Technology32 nm32 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 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 8450G (533 - 720 MHz)
Architecturex86x86x86
Announced

Benchmarks

Cinebench R15 - Cinebench R15 CPU Multi 64 Bit
min: 117     avg: 117.5     median: 117.5 (1%)     max: 118 Points
Cinebench R15 - Cinebench R15 CPU Single 64 Bit
min: 54     avg: 63.5     median: 63.5 (22%)     max: 73 Points
Cinebench R11.5 - Cinebench R11.5 CPU Multi 64 Bit
min: 2.14     avg: 2.2     median: 2.2 (4%)     max: 2.31 Points
min: 1     avg: 1.2     median: 1.2 (2%)     max: 1.34 Points
Cinebench R11.5 - Cinebench R11.5 CPU Single 64 Bit
min: 0.87     avg: 0.9     median: 0.9 (3%)     max: 0.89 Points
min: 0.64     avg: 0.8     median: 0.7 (2%)     max: 0.87 Points
Cinebench R10 - Cinebench R10 Rend. Single (32bit)
2182 Points (19%)
min: 2389     avg: 2490     median: 2480.5 (22%)     max: 2610 Points
Cinebench R10 - Cinebench R10 Rend. Multi (32bit)
3774 Points (5%)
min: 2990     avg: 3740     median: 3956 (5%)     max: 4057 Points
Cinebench R10 - Cinebench R10 Rend. Multi (64bit)
8232 Points (7%)
min: 3558     avg: 4653     median: 4823 (4%)     max: 5407 Points
Cinebench R10 - Cinebench R10 Rend. Single (64bit)
3247 Points (20%)
min: 2838     avg: 3259     median: 3377 (21%)     max: 3444 Points
wPrime 2.10 - wPrime 2.0 1024m *
901 s (11%)
1324 s (16%)
wPrime 2.10 - wPrime 2.0 32m *
28.7 s (6%)
min: 39.8     avg: 40.9     median: 40.9 (8%)     max: 41.92 s
WinRAR - WinRAR 4.0
1266 Points (7%)
min: 1120     avg: 1169     median: 1169 (7%)     max: 1218 Points
X264 HD Benchmark 4.0 - x264 Pass 2
7.6 fps (3%)
min: 7.46     avg: 8.2     median: 8.2 (4%)     max: 9 fps
X264 HD Benchmark 4.0 - x264 Pass 1
39.2 fps (11%)
min: 40.25     avg: 43.4     median: 43.4 (12%)     max: 46.5 fps
TrueCrypt - TrueCrypt Serpent
0.1 GB/s (4%)
min: 0.0868     avg: 0.1     median: 0.1 (3%)     max: 0.09 GB/s
TrueCrypt - TrueCrypt Twofish
0.2 GB/s (5%)
min: 0.163     avg: 0.2     median: 0.2 (3%)     max: 0.164 GB/s
TrueCrypt - TrueCrypt AES
1.1 GB/s (4%)
min: 0.808     avg: 0.8     median: 0.8 (3%)     max: 0.814 GB/s
3DMark 06 - CPU - 3DMark 06 - CPU
2986 Points (6%)
min: 1581     avg: 1793     median: 1649 (4%)     max: 2148 Points
Super Pi mod 1.5 XS 1M - Super Pi mod 1.5 XS 1M *
39 s (8%)
min: 28.9     avg: 29     median: 29 (6%)     max: 29.17 s
Super Pi mod 1.5 XS 2M - Super Pi mod 1.5 XS 2M *
86 s (4%)
69 s (3%)
Super Pi Mod 1.5 XS 32M - Super Pi mod 1.5 XS 32M *
2237 s (10%)
1657 s (7%)
SiSoft Sandra Dhrystone (MIPS) - SiSoft Sandra Dhrystone (MIPS)
33372 MIPS (16%)
17160 MIPS (8%)
SiSoft Sandra Whetstone (MFLOPS) - SiSoft Sandra Whetstone (MFLOPS)
22906 MFLOPS (18%)
12710 MFLOPS (10%)
3DMark Vantage - 3DM Vant. Perf. CPU no Physx
6493 Points (7%)
min: 2764     avg: 3371     median: 3404 (3%)     max: 3946 Points
3DMark 11 - 3DM11 Performance Physics
min: 2533     avg: 2709     median: 2772 (10%)     max: 2823 Points
min: 942     avg: 1357     median: 1414.5 (5%)     max: 1656 Points
3DMark - 3DMark Ice Storm Physics
min: 11808     avg: 14488     median: 15493 (10%)     max: 15980 Points
3DMark - 3DMark Ice Storm Extreme Physics
16269 Points (13%)
3DMark - 3DMark Ice Storm Unlimited Physics
17364 Points (15%)
3DMark - 3DMark Cloud Gate Physics
min: 907     avg: 1117     median: 1220 (3%)     max: 1294 Points
3DMark - 3DMark Fire Strike Standard Physics
min: 1185     avg: 1539     median: 1713 (4%)     max: 1804 Points
Geekbench 2 - 32 Bit - Geekbench Stream
3509 Points (28%)
Geekbench 2 - 32 Bit - Geekbench Memory
3223 Points (29%)
Geekbench 2 - 32 Bit - Geekbench Floating Point
3891 Points (8%)
Geekbench 2 - 32 Bit - Geekbench Integer
3103 Points (6%)
Geekbench 2 - 32 Bit - Geekbench Total Score
3443 Points (9%)
Sunspider - Sunspider 1.0 Total Score *
min: 164     avg: 223     median: 247 (3%)     max: 258 ms
Octane V2 - Octane V2 Total Score
min: 8944     avg: 11205     median: 10252 (11%)     max: 14419 Points

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

Average Benchmarks AMD A6-5350M → 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 12. 07:24:15

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

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

#2 checking url part for id 4157 +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 Thu, 11 Aug 2022 13:13:36 +0200 +0s ... 0s

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

#6 linkCache_getLink no uid found +0.006s ... 0.014s

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

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

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

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

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

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

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

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

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

#16 linkCache_getLink no uid found +0.003s ... 0.017s

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

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

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

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

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

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

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

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

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

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

#27 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.017s

#28 composed specs +0s ... 0.017s

#29 did output specs +0s ... 0.017s

#30 getting avg benchmarks for device 3747 +0s ... 0.017s

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

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

#33 got single benchmarks 3747 +0.007s ... 0.025s

#34 getting avg benchmarks for device 3780 +0s ... 0.025s

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

#36 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.027s

#37 got single benchmarks 3780 +0.01s ... 0.036s

#38 getting avg benchmarks for device 4157 +0s ... 0.037s

#39 got single benchmarks 4157 +0s ... 0.037s

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

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

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

#43 linkCache_getLink no uid found +0.001s ... 0.038s

#44 linkCache_getLink no uid found +0s ... 0.039s

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

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

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

#48 linkCache_getLink no uid found +0s ... 0.039s

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

#50 linkCache_getLink no uid found +0s ... 0.04s

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

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

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

#54 linkCache_getLink no uid found +0s ... 0.041s

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

#70 linkCache_getLink no uid found +0s ... 0.043s

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

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

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

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

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

#76 linkCache_getLink no uid found +0s ... 0.045s

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

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

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

#80 linkCache_getLink no uid found +0s ... 0.045s

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

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

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

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

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

#86 linkCache_getLink no uid found +0s ... 0.047s

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

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

#89 linkCache_getLink no uid found +0s ... 0.048s

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

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

#92 linkCache_getLink no uid found +0s ... 0.048s

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

#94 linkCache_getLink no uid found +0s ... 0.049s

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

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

#97 linkCache_getLink no uid found +0s ... 0.05s

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

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

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

#101 linkCache_getLink no uid found +0s ... 0.051s

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

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

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

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

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

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

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

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

#110 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.054s

#111 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.054s

#112 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.054s

#113 linkCache_getLink no uid found +0s ... 0.054s

#114 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.054s

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

#116 linkCache_getLink no uid found +0s ... 0.055s

#117 linkCache_getLink no uid found +0s ... 0.055s

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

#119 linkCache_getLink no uid found +0s ... 0.055s

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

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

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

#123 linkCache_getLink no uid found +0s ... 0.055s

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

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

#126 linkCache_getLink no uid found +0s ... 0.055s

#127 linkCache_getLink no uid found +0s ... 0.056s

#128 linkCache_getLink no uid found +0s ... 0.056s

#129 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.057s

#130 linkCache_getLink no uid found +0s ... 0.057s

#131 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.057s

#132 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.057s

#133 linkCache_getLink no uid found +0s ... 0.057s

#134 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.057s

#135 linkCache_getLink no uid found +0s ... 0.057s

#136 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.057s

#137 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.057s

#138 linkCache_getLink no uid found +0s ... 0.057s

#139 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.058s

#140 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.058s

#141 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.058s

#142 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.059s

#143 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.059s

#144 linkCache_getLink no uid found +0s ... 0.059s

#145 linkCache_getLink no uid found +0s ... 0.059s

#146 linkCache_getLink no uid found +0s ... 0.06s

#147 linkCache_getLink no uid found +0s ... 0.06s

#148 linkCache_getLink no uid found +0s ... 0.06s

#149 linkCache_getLink no uid found +0s ... 0.06s

#150 min, max, avg, median took s +0s ... 0.06s

#151 return log +0s ... 0.06s

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)