Single page Print


JavaScript performance
We tested JavaScript performance using the SunSpider and Kraken benchmarks running in Google Chrome.

The A8-7600 is stuck between Haswell and Richland here. The Core i3-4330 has a considerable lead over the fastest Kaveri config, which in turn has a smaller advantage over the A10-6700T.

TrueCrypt disk encryption
TrueCrypt supports acceleration via Intel's AES-NI instructions, which also work with Richland and Kaveri. We've included results for another algorithm, Twofish, that isn't accelerated via dedicated instructions.

In the AES test, the Core i3-4330 slips between the two Kaveri configs. It's not fast enough to keep up in the Twofish test, though. The A10-6700T isn't fast enough to keep up with the A8-7600 in either test.

7-Zip file compression and decompression
The first of two compression tests, 7-Zip doesn't employ any specialized hardware acceleration.

The A8-7600 fares reasonably well here. Its 65W incarnation is only a smidgen behind the Core i3-4330 in the compression test, and it has a comfortable lead over the Intel chip in the decompression test. Capping the chip's TDP at 45W lowers performance somewhat, but the A8-7600 still performs better than the A10-6700T in the same thermal envelope. With slower CPU and memory frequencies, the A8-6500T continues to bring up the rear.

WinZip file compression and decompression
Unlike Z-Zip, WinZip has built-in OpenCL acceleration. It doesn't include a benchmark, so we used a stopwatch to time how long it took to compress and decompress 1.5GB of application, MP3, RAW, JPEG, Excel, and text files.

Although the A8-7600 compresses our file set in about the same amount of time as the Core i3-4330, the Intel chip is much faster in the decompression test. Interestingly, the Richland-based A10-6700 is way behind in the compression test but barely off the pace in the decompression test.

Compiling code in GCC
Our resident developer, Bruno Ferreira, helped put together this code compiling test. Qtbench tests the time required to compile the QT SDK using the GCC compiler. Here's Bruno's note about how he built it:

QT SDK 2010.05 - Windows, compiled via the included MinGW port of GCC 4.4.0.

Even though apparently at the time the Linux version had properly working and supported multithreaded compilation, the Windows version had to be somewhat hacked to achieve the same functionality, due to some batch file snafus.

After a working multithreaded compile was obtained (with the number of simultaneous jobs configurable), it was time to get the compile time down from 45m+ to a manageable level. This required severe hacking of the makefiles in order to strip the build down to a more streamlined version that preferably would still compile before hell froze over.

Then some more fiddling was required in order for the test to be flexible about the paths where it was located. Which led to yet more Makefile mangling (the poor thing).

The number of jobs dispatched by the Qtbench script is configurable, and the compiler does some multithreading of its own, so we did some calibration testing to determine the optimal number of jobs for each CPU.

Score another one for the Core i3-4330. The A8-7600 takes more than a minute longer to finish our compiling test, and that's in 65W mode. Lowering the TDP extends the chip's compiling time by about a minute and a half, putting it even farther behind. At least the A8-7600 has a healthy advantage over the A10-6700T. The gap between the Kaveri chip and its closest Richland competition is large enough to suggest that IPC improvements are partially responsible.