Workstation Applications

Visual Studio 6

Carried over from our previous CPU reviews, we continue to use Visual Studio 6 for a quick compile test. We are still using the Quake 3 source code as our test and measure compile time in seconds. The results are pretty much in line with what we've seen in the past.

Without compiler speed optimizations for NetBurst, the Pentium 4 architecture is not very well suited for highly branchy applications such as compiling and code optimization. The Athlon 64 is far better suited for this type of usage pattern and thus AMD wins the compiler test.

Visual Studio 6 Compiler Performance

SPECviewperf 8

For our next set of professional application benchmarks we turn to SPECviewperf 8. SPECviewperf is a collection of application traces taken from some of the most popular professional applications, and compiled together in a single set of benchmarks used to estimate performance in the various applications the benchmark is used to model. With version 8, SPEC has significantly improved the quality of the benchmark, making it even more of a real world indicator of performance.

We have included SPEC's official description of each one of the 8 tests in the suite.

3dsmax Viewset (3dsmax-03)

"The 3dsmax-03 viewset was created from traces of the graphics workload generated by 3ds max 3.1. To insure a common comparison point, the OpenGL plug-in driver from Discreet was used during tracing.

The models for this viewset came from the SPECapc 3ds max 3.1 benchmark. Each model was measured with two different lighting models to reflect a range of potential 3ds max users. The high-complexity model uses five to seven positional lights as defined by the SPECapc benchmark and reflects how a high-end user would work with 3ds max. The medium-complexity lighting models uses two positional lights, a more common lighting environment.

The viewset is based on a trace of the running application and includes all the state changes found during normal 3ds max operation. Immediate-mode OpenGL calls are used to transfer data to the graphics subsystem."

The biggest surprise here is that there is a huge performance impact (13%) by moving down to a single channel memory subsystem with the Athlon 64. There are also a couple of other surprises, with the Pentium 4 560 doing surprisingly well, coming in at the heels of the Athlon 64 FX-55.

SPECviewperf 8 - 3dsmax 3.1 Performance

CATIA Viewset (catia-01)

"The catia-01 viewset was created from traces of the graphics workload generated by the CATIATM V5R12 application from Dassault Systemes.
Three models are measured using various modes in CATIA. Phil Harris of LionHeart Solutions, developer of CATBench2003, supplied SPEC/GPC with the models used to measure the CATIA application. The models are courtesy of CATBench2003 and CATIA Community.

The car model contains more than two million points. SPECviewperf replicates the geometry represented by the smaller engine block and submarine models to increase complexity and decrease frame rates. After replication, these models contain 1.2 million vertices (engine block) and 1.8 million vertices (submarine).

State changes as made by the application are included throughout the rendering of the model, including matrix, material, light and line-stipple changes. All state changes are derived from a trace of the running application. The state changes put considerably more stress on graphics subsystems than the simple geometry dumps found in older SPECviewperf viewsets.

Mirroring the application, draw arrays are used for some tests and immediate mode used for others."

The single channel Athlon 64 3400+ does exceptionally poorly here, with the dual channel Athlon 64 parts holding a significant performance advantage. By now it's no surprise to see the FX-55, 4000+ and 3800+ at the top of the charts.

Interestingly enough, the CATIA benchmark appears to favor Intel's Prescott core over Northwood.

SPECviewperf 8 - CATIA V5R12 Performance

EnSight (ensight-01)

"The ensight-01 viewset replaces the Data Explorer (dx) viewset. It represents engineering and scientific visualization workloads created from traces of CEI's EnSight application.

CEI contributed the models and suggested workloads. Various modes of the EnSight application are tested using both display-list and immediate-mode paths through the OpenGL API. The model data is replicated by SPECviewperf 8.0 to generate 3.2 million vertices per frame.

State changes as made by the application are included throughout the rendering of the model, including matrix, material, light and line-stipple changes. All state changes are derived from a trace of the running application. The state changes put considerably more stress on graphics subsystems than the simple geometry dumps found in older viewsets.

Mirroring the application, both immediate-mode and display-list modes are measured."

No 925X based test system would complete this test, thus all we have are AMD chips to look at. Once again we see that the 3400+ is seriously crippled by its single channel memory interface.

SPECviewperf 8 - EnSight Performance

Lightscape Viewset (light-07)

"The light-07 viewset was created from traces of the graphics workload generated by the Lightscape Visualization System from Discreet Logic. Lightscape combines proprietary radiosity algorithms with a physically based lighting interface.

The most significant feature of Lightscape is its ability to accurately simulate global illumination effects by precalculating the diffuse energy distribution in an environment and storing the lighting distribution as part of the 3D model. The resulting lighting "mesh" can then be rapidly displayed."

SPECviewperf 8 - Lightscape Visualization System Performance

Maya Viewset (maya-01)

"The maya-01 viewset was created from traces of the graphics workload generated by the Maya V5 application from Alias.

The models used in the tests were contributed by artists at NVIDIA. Various modes in the Maya application are measured.

State changes as made by the application are included throughout the rendering of the model, including matrix, material, light and line-stipple changes. All state changes are derived from a trace of the running application. The state changes put considerably more stress on graphics subsystems than the simple geometry dumps found in older viewsets.

As in the Maya V5 application, array element is used to transfer data through the OpenGL API."

SPECviewperf 8 - Maya V5 Performance

Pro/ENGINEER (proe-03)

"The proe-03 viewset was created from traces of the graphics workload generated by the Pro/ENGINEER 2001TM application from PTC.

Two models and three rendering modes are measured during the test. PTC contributed the models to SPEC for use in measurement of the Pro/ENGINEER application. The first of the models, the PTC World Car, represents a large-model workload composed of 3.9 to 5.9 million vertices. This model is measured in shaded, hidden-line removal, and wireframe modes. The wireframe workloads are measured both in normal and antialiased mode. The second model is a copier. It is a medium-sized model made up of 485,000 to 1.6 million vertices. Shaded and hidden-line-removal modes were measured for this model.

This viewset includes state changes as made by the application throughout the rendering of the model, including matrix, material, light and line-stipple changes. The PTC World Car shaded frames include more than 100MB of state and vertex information per frame. All state changes are derived from a trace of the running application. The state changes put considerably more stress on graphics subsystems than the simple geometry dumps found in older viewsets.

Mirroring the application, draw arrays are used for the shaded tests and immediate mode is used for the wireframe. The gradient background used by the Pro/E application is also included to better model the application workload."

When the Athlon was first released, it was a very solid performer in Pro/ENGINEER. But of course, back then, very few companies would think about Athlon workstations. With the Athlon 64 times have obviously changed, but the performance advantage does not seem to have changed at all, AMD continues to lead the way in the proe-03 viewset.

SPECviewperf 8 - Pro/ENGINEER Performance

SolidWorks Viewset (sw-01)

"The sw-01 viewset was created from traces of the graphics workload generated by the Solidworks 2004 application from Dassault Systemes.

The model and workloads used were contributed by Solidworks as part of the SPECapc for SolidWorks 2004 benchmark.

State changes as made by the application are included throughout the rendering of the model, including matrix, material, light and line-stipple changes. All state changes are derived from a trace of the running application. The state changes put considerably more stress on graphics subsystems than the simple geometry dumps found in older viewsets.

Mirroring the application, draw arrays are used for some tests and immediate mode used for others."

SPECviewperf 8 - Solidworks 2004 Performance

Unigraphics (ugs-04)

"The ugs-04 viewset was created from traces of the graphics workload generated by Unigraphics V17.

The engine model used was taken from the SPECapc for Unigraphics V17 application benchmark. Three rendering modes are measured -- shaded, shaded with transparency, and wireframe. The wireframe workloads are measured both in normal and anti-alised mode. All tests are repeated twice, rotating once in the center of the screen and then moving about the frame to measure clipping performance.

The viewset is based on a trace of the running application and includes all the state changes found during normal Unigraphics operation. As with the application, OpenGL display lists are used to transfer data to the graphics subsystem. Thousands of display lists of varying sizes go into generating each frame of the model.

To increase model size and complexity, SPECviewperf 8.0 replicates the model two times more than the previous ugs-03 test."

SPECviewperf 8 - Unigraphics V17

3D Rendering Performance Power Consumption Comparison
Comments Locked

89 Comments

View All Comments

  • Live - Tuesday, October 19, 2004 - link

    Splendid reading! This site is doing a great job right now. I really would love more of these very informative articles that help you so at seeing the big picture.

    A really helpful article.
  • Disorganise - Tuesday, October 19, 2004 - link

    I’m a bit disappointed by you inconsistency…

    The comparison with Intel over who wins….slightly inconsistent but no biggie.

    What really is bad though, is the penultimate page – is socket 939 worth it?

    I agree it is but…..
    You’ve taking an identical chip and found it about 5% quicker than on socket 754. OK, no problem. But AMD have wacked a whopping 12% increase in rating, to 3800+ from 3400+. It doesn’t gel, the numbers don’t work.

    The 3800+ is also more expensive than the 3400+ to the tune of about 250% here in Australia and about 220% over there in the U.S. a 5% increase in performance does not warrant a doubling in price.

    Dave
  • at80eighty - Tuesday, October 19, 2004 - link

    way to go Anand...excellently comprehensive article...

    /waiting for those HDD articles you promised : p
  • SLIM - Tuesday, October 19, 2004 - link

    Going along with what #6 said:
    Athlon 64 4000+ - 2.4GHz - 1MB - 128-bit
    Athlon 64 3800+ - 2.4GHz - 512KB - 128-bit
    Athlon 64 3400+ - 2.4GHz - 1MB - 64-bit <---should be a socket 754 3700+ right?
    Athlon 64 3400+ - 2.4GHz - 512KB - 64-bit
    Athlon 64 FX-53 - 2.4GHz - 1MB - 128-bit

    SLIM
  • ViRGE - Tuesday, October 19, 2004 - link

    #12, even GPUs aren't going anywhere fast. There's still a shortage of something or other needed to make the Ultra/PE parts, and there isn't a planned refresh for 2004. ATI/Nvidia have another speed grade of RAM to jump to(1.6ghz GDDR3), and can die-shrink down to 90nm once TSMC gets there, but they're so close to CPUs right now, they're destined to hit the same wall too.

    Anand, someone has been a busy beaver.;-) That was a long, but well thought out and informative article; you've basically written the definitive CPU article for now until the multicores come out.
  • Tides - Tuesday, October 19, 2004 - link

    Ah I read the conclusion wrong.
  • Tides - Tuesday, October 19, 2004 - link

    why is this site putting down an amd performance gain and making excuses for intel at the same time.
  • Doormat - Tuesday, October 19, 2004 - link

    Its a shame the processor wars are coming to an end. I see dual core as neat, but a dud performance wise. It'll be another year or two before the GPU wars start to die out... hmmm..

    -CPU performance levels off
    -HD capacity levels off

    The only interesting stuff going on is GPU stuff.
  • dvinnen - Tuesday, October 19, 2004 - link

    Best artical from Anandtech I've read in a long time. Good job Anand.
  • skiboysteve - Tuesday, October 19, 2004 - link

    wait nevermind, you put your comments ABOVE the graphs. threw me off cause this isnt what you usualy do...

Log in

Don't have an account? Sign up now