FurMark
Current Version: 1.15.0
»FurMark homepage
»FurMark 1.9.x Submissions

GPU Caps Viewer
Current Version: 1.22.0
»GPU Caps Viewer homepage
»GPU DB Submissions

PhysX FluidMark
Current Version: 1.5.2
»FluidMark homepage
»FluidMark 1.4.x Submissions

GeeXLab
Current Version: 0.4.0
»GeeXLab homepage
»GeeXLab Overview

GPU Shark
Current Version: 0.9.2
»GPU Shark homepage

TessMark
Current Version: 0.3.0
»TessMark homepage

ShaderToyMark
Current Version: 0.3.0
»ShaderToyMark homepage
»ShaderToyMark Scores

Blogs
»JeGX's HackLab

Geeks3D's Articles
»GPU Memory Speed Demystified

»Multi-Threading Programming Resources

»GeForce and Radeon OpenCL Overview

»How to Get your Multi-core CPU Busy at 100%

»How To Make a VGA Dummy Plug

»Night Vision Post Processing Filter


Demoniak3D
Current Version: 1.23.0
»Demoniak3D
»Download
»Libraries and Plugins
»Demos
»Online Help - Reference Guide
»Codes Samples

Language

Language:

3D Graphics Search Engine:

The Geeks Of 3D

 


AOGenMark - Multi-core CPU benchmark

Download

AOGenMark 1.3.0 - WinXP / Vista / Win7


What is AOGenMark?

AOGenMark is a tiny command line tool that allows you to bench your brand new CPU. AOGenMark is based on the very old AOGen tool (see AOGen - Ambient occlusion maps generation). The main problem of AOGen tool is its slowness because of the bruteforce approach used to compute the AO data. The algorithm used in AOGen is described here: AOGen algorithm @ oZone3D.Net forums.



It's too slow but actually it's good for a CPU benchmark. The principle of the benchmark is quite simple: the smaller the elapsed time to finish the bench, the faster your CPU. The elapsed time is provided in milliseconds so you can measure with accuracy the impact of your overcloking parameters on the CPU/memory.

The main feature of AOGenMark is its multi-core (or multi-threaded) capability. You can use AOGenMark to benchmark a n-core CPU. Just set the number of threads you want (2, 4, 8, 10, 24, ...).

AOGenMark has several parameters in command line and the two most important are: the number of threads and the number of samples. By default, the number of samples is 8 while the number of threads is the number of logical cores detected.

If you wish to use AOGenMark to check the stability of your system, you can set the number of samples to a higher value like 32, 64, 128, 512, 1024.... With 1024 samples, the bench will last many hours or days... See the readme.txt file in the zip archive for more information about parameters.




A comparative table of scores can be found HERE.






GLSL Hacker
»GLSL Hacker Homepage


PhysX 3 cloth demo


Normal visualizer with GS


Compute Shaders test on Radeon


Raymarching in GLSL



Geeks3D latest news


Geeks3D forum news


Misc
»Texture DataPack #1
»Asus Silent Knight CPU Cooler
Page generated in 0.080413818359375 seconds.