AMD Sempron 3400+ Launch

Article Index

Futuremark PCMark05 & 3DMark05 - CPU Testing Module

FutureMark PCMark05
More Synthetic CPU & Memory Benchmarks

We continued our synthetic testing with PCMark05, the latest all-in-one benchmark to be released from the team at FutureMark.  Here we focused on CPU and Memory performance, comparing the results to a Sempron 3300+, 3100+ and Intel Celeron D 335.

When we compare the results with the CPU module, we found the Celeron D 335 to offer the highest performance, besting all three Sempron processors.  Of the AMD chips, the Sempron 3400+ was the top performer, slightly beating out the 3300+ with half of the L2 cache.  Memory performance was also reporting the strongest results with the Celeron D 335, with the Sempron 3400+ being the fastest of the three Sempron processors.  Note how the quantity of L2 cache has an apparent effect on the memory performance results in PCMark05.  In SANDRA, the memory scores were identical, but with PCMark05, the scores imply that memory performance is slower with the Sempron 3300+ and its 128KB of L2 cache compared to the Semprons 3100+ and 3400+ outfitted with 256KB of L2 Cache.

3DMark05 - CPU Testing Module
DirectX Gaming Performance

While 3DMark05 is typically used for benchmarking graphics cards, it's also versatile enough to isolate testing to the CPU, making it a useful tool for testing CPU and motherboard performance.  In this round of tests, we ran 3DMark05's CPU test exclusively, logging the results with each processor.

With 3DMark05's CPU performance module, the Sempron 3400+ took the top spot, beating the Sempron 3300+ by roughly 200 3DMarks.  The Sempron 3100+ was the slowest of the three Semprons, trailing the 3400+ by 466 3DMarks.  Interestingly, PCMark05's testing procedures show Intel's Celeron D 335 as being the best performing CPU, yet 3DMark05's CPU module lists it as the slowest overall performer, hampered by its low 28KB of L1 cache.

Tags:  AMD, launch, pro, Sempron, AM

Related content

Comments

Show comments blog comments powered by Disqus