This is an old revision of the document!
Let's do some VIS benchmarking
Setup and execution
All links here point to mirrors at Quaddiced to prevent link-rot.
Download https://www.quaddicted.com/filebase/gmsp3.zip and extract it. Make a copy of the gmsp3v2.bsp file.
Download https://www.quaddicted.com/files/tools/visbjp.zip and extract it. Run
Bspinfo.exe -prt gmsp3v2.bsp
Download https://www.quaddicted.com/files/tools/wvis_20100119.7z and extract it. Run
WVis.exe gmsp3v2.bsp
Remove the generated gmsp3v2.bsp file and recreated it by making a copy of the copy you made earlier.
Download https://www.quaddicted.com/files/tools/tyrutils-0.5-win32.zip and extract it. Here you find vis.exe in the bin/ subdirectory. Run
vis.exe gmsp3v2.bsp
If you are on Linux, use https://www.quaddicted.com/files/tools/tyrutils-0.5.tar.gz . Just make
, it will build a binary named vis in the bin/ directory.
Then add your times and information about your processor to the table below. If you are running with a non-standard frequency, please add that. Please add entries ordered by time, if in doubt by the time of the tyrutils. The top entry should be the fastest.
Results
"Linux/Wine" means that WVis was run in Wine as it is not available as native binary. WVis already rounds to full minutes.
Processor | Platform | WVis | tyrutils' vis | Name |
---|---|---|---|---|
i5-3470 | Linux/Wine | 13min | 67s | Spirit |