Welcome to Cornucopia3D

Cornucopia3D: The World of Plenty!

On Cornucopia3D, you will find all sorts of resources to improve your 3D experience: forums, galleries, portfolios, tutorials, ... as well as a store where you can find top-quality content at the best possible price!

Member Login

Forgotten your password?






Not a member yet? Sign Up!


Cornucopia3D • View topic - VueMark : a benchmark for Vue 6 Infinite

VueMark : a benchmark for Vue 6 Infinite

For general discussions about the Vue product line. Any topic that does not fit in one of the following forums should be posted here.

VueMark : a benchmark for Vue 6 Infinite

Note : If you are interested in everything related to Vue 6 performance (hardware optimization and multithreading, 64-bit vs 32-bit differences, influence of cpu and memory on render speed, etc.) feel free to download the 'Vue 6 Performance analysis' PDF document here : http://renderfred.free.fr/articles.html (most recent version 1.04 - updated on July 1st, 2007)

UPDATE 2007/08/21 : v1.3, recalibrated for V6I 6.50 - build 291733
The entire database has been refreshed. As significant speed increases have been made in the recent major version (6.5), old times are not comparable with new ones. The only values accepted in the new database will be those done with the VueMark 1.3 and V6I 6.5 (build >= 291733).

I am glad to present the VueMark 1.3 rendering benchmark for Vue 6 Infinite (sorry, not Esprit / Pro Studio / Easel, as scores cannot be directly compared). It is composed of 3 tests, based on scenes provided on the Extras CD of V6I :

'Peaking Through' (outdoor, procedural terrain, metaclouds)
'RadiosityRoom' (indoor, radiosity)
'Cerro Verde' (outdoor, big vegetation ecosystem)

Image

- The benchmark is easy to use. The user just has to run a Python script and wait for the benchmark to finish. No need to load each scene and adjust render settings manually anymore.
- It is accurate. It measures the total render time, including the preparation phase for radiosity (which can be quite long but is never displayed by Vue...).
- The script eliminates possible user errors (selecting the wrong resolution or render quality, etc.)

To run the VueMark, make sure that the ‘Post Render Options’ dialog is deactivated (it appears by default after a render), or it would stop the benchmark. Then, follow these steps :

1 - Download the VueMark python script -> http://renderfred.free.fr/utils/VueMark.zip and unzip the script.
2 - Create a 'VueMark' subdirectory under the '\Vue 6 Infinite\Python' directory. Put the VueMark.py script and the three benchmark scenes (01_Peaking Through.vue, 08_RadiosityRoom.vue and 05_Cerro Verde.vue) in this '\Vue 6 Infinite\Python\VueMark' directory.
3 - Load Vue 6 Infinite
4 - Run the VueMark.py script with the menu command 'Python/Run Python script...' (and browse to locate the script on your hard disk).
Please verify that you are running at least the 1.3 version of the benchmark (the VueMark version is displayed in the first requester). If the version is not displayed, you have an old version.
5 - Wait until the three benchmarks are finished. In the same directory, you will find a 'VueMark<32/64>_<name>.txt' file which contains the results.
6 - Copy the content of this text file and paste it in this thread.

Note that the VueMark score is 100 for a Pentium 4C @ 3.0 GHz. A computer with a VueMark score of 200 is twice as fast as this reference computer.

Below is the VueMark database, which will be regularly edited to enter new scores.

VueMark 1.3 database (online since 08/22-2007)
Score : CPU - Frequency (Nb cores - Vue build - os)

'ovck' = overclocked system. Note: if you overclock your system, I suggest you test it for stability with CPUStressMT (http://olivier.fouge.free.fr/CPUStressMT). Please run the test for at least an hour. It detects instabilities much faster than, for instance, Prime number testing. I trust you to enter only stable overclocking results :wink: .

64-bit scores
=========


898 : Dual Xeon 5355 - 2.66 GHz (8-core - 291733 - xp64)
753 : Core 2 Extreme QX6700 - 3.70 GHz (4-core - ovck - 291733 - xp64)
634 : Core 2 Quad Q6600 - 3.00 GHz (4-core - ovck - 291733 - vista64)
527 : Core 2 Quad Q6600 - 2.40 GHz (4-core - 291733 - vista64)
510 : MacPro - 2.66 GHz (4-core - 291733 - xp64)

502 : Core 2 Quad Q6600 - 2.40 GHz (4-core - 292230 - vista64)
500 : Dual Opteron 285 - 2.60 GHz (4-core - 291733 - xp64)
428 : Dual Opteron 275 - 2.25 GHz (4-core - 291733 - xp64)
418 : Dual Opteron 275 - 2.25 GHz (4-core - 291733 - vista64)
408 : Core 2 Duo E6600 - 3.60 GHz (2-core - ovck - 291733 - vista64)

285 : Athlon 64 X2 5200+ - 2.61 GHz (2-core - 291733 - xp64)
270 : Core 2 Duo E6300 - 2.40 GHz (2-core - 291733 - xp64)
234 : Athlon 64 X2 4400+ - 2.21 GHz (2-core - 291733 - os unknown)

32-bit scores
=========


709 : Core 2 Extreme QX6700 - 3.70 GHz (4-core - ovck - 291733 - xp32)
573 : Core 2 Quad Q6600 - 3.20 GHz (4-core - ovck - 291733 - os unknown)
511 : MacPro - 3.00 GHz (4-core - 291733 - leopard)
492 : MacPro - 3.00 GHz (4-core - 291733 - macos10)
444 : MacPro - 2.66 GHz (4-core - 291733 - macos10)

441 : Dual Opteron 285 - 2.60 GHz (4-core - 291733 - xp32)
344 : Dual Opteron 275 - 2.25 GHz (4-core - 291733 - xp32)
307 : Dual Opteron 275 - 2.25 GHz (4-core - 291733 - vista32)
267 : Athlon X2 5600+ - 2.80GHz (2-core - 291733 - os unknown)
230 : Core 2 Duo E6700 - 2.66 GHz (2-core - 291733 - vista32)

225 : Core 2 Duo E6400 - 2.13 GHz (2-core - 292350 - os unknown)
222 : MacBook Pro - ?.? GHz - (2-core - 291733 - macos10)
182 : Athlon 64 X2 3800+ - 2.00 GHz (2-core - 291733 - xp32)
167 : Centrino Duo - 1.60 GHz (2-core - 291733 - vista32)
100 : Pentium 4C - 3.00 GHz (1-core - 291733 - xp32)
99 : Athlon 64 - 800 MHz (1-core - 291733 - xp32)

Happy VueMarking !
Last edited by Frederic Louguet on January 18, 2008, edited 84 times in total.
This post: December 14, 2006

by

User avatar
Frederic Louguet
Posts: 485
Joined: July 31, 2005

Fantastic work Frederic - what a great idea & VueMark tool!

I expect this thread will be a very frequently visited site for everyone keen to know how to get the most out of their setup, and of course to see how well their system's performance compares to everyone else's...

May the testing begin! 8)

Kind regards
This post: December 14, 2006

by

User avatar
Roderick Davies
Posts: 491
Joined: July 31, 2005

Fantastic Frederic - I was wondering what you were up to. This is a much needed capability and I'm glad you were the one who designed this elegant solution. One question, why broadcast mode for Cerro Verde? I didn't think there was any blur happening in that scene.
This post: December 14, 2006

by

Dave Burdick
Posts: 1044
Joined: August 23, 2005

There are three reasons for broadcast mode for Cerro verde :

1) In the Vue 5 Infinite benchmark it was already broadcast mode.
2) That way the render times of the three scenes are relatively close.
3) It is a test to see if the benchmarker is alert (final, final, fin.. oh wait no... broadcast !) :wink:
This post: December 14, 2006

by

User avatar
Frederic Louguet
Posts: 485
Joined: July 31, 2005

Excellent idea :D

But, I have a question.
All the scenes will load/render at the requested settings in Vue 6 Esprit but the Cerro Verde scene takes around twice as long as the other two scenes to render.

This gives a VueMark score lower than I would expect for my system,
if I halve the Cerro verde time it gives a result around what I would expect (for V6I).

My question is;
Is the benchmark compatible with Vue 6 Esprit or am I missing something when I set up Cerro verde for rendering (3 tests all around 23-24mins compared to 11-12mins for the other 2 tests)?
This post: December 14, 2006

by

User avatar
Andrew Walters
Posts: 8
Joined: August 08, 2006

Andrew,

The benchmark is for Vue 6 Infinite and has not been tested with the other Vue versions. I do not have Vue 6 Esprit, but it would not surprise me if the render parameters were different. If someone who has Esprit and Infinite could do some comparisons we would know for sure, but until then the benchmark is specifically for Infinite.

Also, as Esprit / Pro Studio / Easel do not support more than two rendering threads, they cannot fully use quad core machines, so it would be better if they had their own benchmark.
This post: December 14, 2006

by

User avatar
Frederic Louguet
Posts: 485
Joined: July 31, 2005

I fully understand :)

For your information my render data is:

AMD64 4200+ @ 2.4GHz (overclocked)
2GB RAM
6800GT graphics (not that it should matter
XP pro 32 bit

Peeking = 12:18
Radiosity = 11:17
Cerro Verde = 23:26

VueMark =187
This post: December 14, 2006

by

User avatar
Andrew Walters
Posts: 8
Joined: August 08, 2006

My numbers:

Peeking through = 12:42
Radiosity room = 10:54
Cerro Verde = 9:12

VUE MARK: 240

(288741)64 bit

AMD Athalon 64x2 4200+ @ 2.2GHz
4 GB RAM
XP pro 64 bit
:D

Oh yeah, almost forgot...My first post here :oops: ...Hi everyone
mike
This post: December 14, 2006

by

User avatar
Mike M
Posts: 324
Joined: October 31, 2006

Welcome Mike, a useful first post !
This post: December 15, 2006

by

User avatar
Frederic Louguet
Posts: 485
Joined: July 31, 2005

I included new results for the Intel Core 2 Extreme QX6700 CPU. The speed of two Xeons 5140 (or 5160 if 10% overclocked) on one CPU !
This post: December 17, 2006

by

User avatar
Frederic Louguet
Posts: 485
Joined: July 31, 2005

Hi,

i'm using Vue6 ProStudio (32 bit). My results :

Peaking through, Final, 1024x768 - 07'56''
Radiosity Room, Final, 1024x463 - 07'35"
Cerro Verde, Broadcast, 1024x768 - 05'49"

Intel Core 2 Duo E6400 2,13@3,0 Ghz, 2 GB RAM 667@750 Mhz

VueMark : 370

regards
Jazz
This post: December 19, 2006

by

jazz
Posts: 23
Joined: December 11, 2006

Mac Pro 2.66, 4 GB Ram, OS X 10.4.8

Peaking through, Final, 1024x768 - 07'01''
Radiosity Room, Final, 1024x463 - 06'03"
Cerro Verde, Broadcast, 1024x768 - 04'42"

VueMark value: 446
This post: December 22, 2006

by

User avatar
Walther Beck
Site Admin
Posts: 4991
Joined: July 30, 2005

Hi Frederic,

I am considering purchasing a new desktop, and really want it to be the best 'bang' for the buck. I'm contemplating a Core 2 Duo 6700 and I have a couple of questions.

1) Do your rendering benchmarks for 64-bit, mean they are running Windows XP64 bit OS? Or, does it mean running the new Vue6-Infinite 64 bit version? Or, are you running the same version as I am (Pentium 4)?

If it is the 64-bit version of Vue, is it any more 'buggy' than the regular release. And on the whole, how much faster would you expect a Core Duo 6700 to be than my 3GHz Pentium 4 with 2GB memory.

2) In your experience, how important is the speed of Ram (DDR2 PC4200 vs DDR2 PC6400) and Non-ECC vs ECC? Also, I'm currently using 2GB on my P4, and very rarely have any memory issue problems. Seeing how expensive the DDR2 PC6400, is it better to get 4GB of the slower memory or 2GB of the faster?

Hope this isn't too much to ask.

Thanks in advance for your help :-)

EDIT:
NEVERMIND. Your extremely well written article mentioned at the top of this thread answered all these questions AND many more! Thanks so very much for this wonderful resource. I encourage EVERYONE to read Frederic's very throrough review of the factors which go into the speed calculation for a Vue render.
This post: January 07, 2007

by

User avatar
Chipp Walters
Posts: 427
Joined: August 17, 2005

Thanks Chipp, I am glad it was useful.
This post: January 07, 2007

by

User avatar
Frederic Louguet
Posts: 485
Joined: July 31, 2005

My VueMark for my Sony Vaio Laptop VGN SZ120P

Processor Intel Core Duo 1.83 GHz
Installed Memory 1 GB (DDR2 SDRAM)
Hard Drive 100 GB Serial ATA, 5400 RPM
Display 13.3 in. XGA TFT LCD
Operating System Microsoft Windows XP Professional
Mobile Technology Intel Centrino Duo Mobile Technology

Peaking Through: 18:39
Radiosity Room: 15:22
Cerro Verde: 12:39

VueMark: 170
This post: January 08, 2007

by

User avatar
Chipp Walters
Posts: 427
Joined: August 17, 2005

Next

Return to Vue - General

cron
 
Recommended screen resolution: 1024 x 768 (best view: Firefox 3, Safari 4, Chrome 9, Internet Explorer 8, Opera 10 or higher).