Navigate:

Advice
Beginners
BIOS Guide
CPUs
Links
Mainboards
Memory
Network
Storage
Video/Sound Cards

Contact
Forum
SiteMap
Sponsors
WebNews
Home
. .

Prices:
CPU
Intel
P4 2.4C-800
P4 2.6C-800
P4 2.8C-800
P4 3.0-800
P4 3.2-800

AMD
AthlonXP
XP 1700+
XP 2000+
XP 2400+
XP 2500+
XP 2700+
XP 3000+
XP 3200+

Athlon64
Athlon64 3200+
Athlon64 FX-51

Opteron
Opteron 240
Opteron 242
Opteron 244
Opteron 246

Memory

Corsair
Crucial
Kingston
Mushkin
OCZ

Search Prices:








































































LOSTCIRCUITS

SHORTCUTS:
Top Page
Mobile Specs
The DFI 855GME-MGF
Test Configurations
Memory Performance
WorldBench5
Sysmark2004
3ds max
Amporphium3, Lightwork, Cinebench
Cinebench2003 Realtime
Gaming Performance
Final Words

Your Comments Can Help Us Improve Our Reviews

 DFI 855GME-MGF and Intel Pentium M 735
Along came a Dothan
(Review by MS, Jan 2, 2005)

3D Rendering

One of the issues that apparently plagues benchmarks centers around applications that may be optimized for one or the other CPU or architecture. In a nutshell, there may be some truth to that but in reality, a lot more simply depends on the actual workload, that is, the model that is being rendered. A classic example is the benchmark suite of 3ds max, comprising CBalls, Single Pipe and Underwater World among others, all of which are dominated by the P4's Netburst architecture. That does not necessarily mean, however that 3ds max is optimized for the P4, the models maybe .. or it could have been the other way around....


There is not much explanation necessary here, the P4 rules but keep in mind that the models rendered are basically using some predefined objects that are transformed and lit and all of that is essentially integer computation. Note that the larger cache does not buy the Dothan anything compared to the Banias here.

Pentium M 735
(Dothan 1.7 GHz)

next page:    => 3dsmax continued =>

If you enjoyed reading this article and found it useful, please consider making a small donation to LostCircuits.
Thank you!

General disclaimer: This page only reflects the author's personal opinion and assumes no responsibility whatsoever regarding any of the contents or any damages that may occur explicitly or implicitly from reading the contents of this site. All names and trademarks mentioned in this review are the exclusive property of the respective parent companies.
All contents of this site are protected by international copyright laws. Reproduction of the contents even in parts is not allowed