MojoWorld3 Benchmark Data

O Frabjous Day! The benchmark page is actually being updated to use MojoWorld 3! If you're looking for the old benchmark page that uses MojoWorld 1.2, you know what to do.

Here's what you need to know about the MojoWorld3 Benchmark:

• To compare your hardware to the data here, start by downloading the v3 benchmark world file - v3benchmark.zip and unzipping it.
• Launch MojoWorld 3 Std or Pro and switch to the Viewer UI (File->Go To Viewer). Alternately, if you are using the free Viewer app, simply launch the Viewer.

  Apologies to users of MojoWorld Focus - because Focus does not have a render queue and because the render settings in Focus cannot be set precisely, Focus cannot be used for this benchmark. Please download either the MojoWorld 3 Std/Pro Demo or the free Viewer to participate in the benchmark!

• Open the v3benchmark.mjw file.
• Open the Uplink Queue panel. Again, note that this is done through the Viewer and not the Render Room, as in the Viewer's Uplink Queue, the final render time will still be displayed when the queue completes.
• Select the benchmark.png job that is already saved in the world file and click the 'save to disk' icon to specify a destination folder for the render.
  

• Click 'Start' to start the Uplink Queue. When it finishes, the render time will be displayed in the lower right-hand corner. The completed render will look like the image shown here, except that the final render size will be 1024x465:
  

• I am no longer updating this page, so compare your results to the existing data. Note that many things not listed here will affect your render times, including but not limited to data bus speeds, hard drive data speeds, background tasks, and so forth. Also note that all of the results below are for MojoWorld 3.0. Some speed improvements were put into the 3.1.1 update.
• Since the video card does not take part in the final render, this benchmark page does not list video card information. For many video cards, a frame rate display can be brought up in the MojoWorld by typing an 'f' where you'd normally use the keyboard navigation keys (make sure input focus is directed to the RTR...). Typing the 'f' key a second time will disable the frame rate readout. Some video cards will report 0.00 FPS because they are not compatible with this particular diagnostic. The diagnostic is merely an engineering tool, not a true feature ;) This diaagnostic readout will not show up if you have a custom render setting selected.

OK, now for some RESULTS! Listed fastest to slowest for your comparison convenience.

Note! The times shown are minutes : seconds . 100ths of seconds!

The rows are color coded per processor type. Yellow for Athlon, lighter yellow for AMD64. Shades of aqua for G4s (darker) and G5s (lighter). Shades of pink for Pentiums, darker for P3s, lighter for P4s. Others left white.