This is an old revision of the document!
Let's do some VIS benchmarking
Setup and execution
All links here point to mirrors at Quaddicted to prevent link-rot.
Download gmsp3.zip and extract it. Make a copy of the gmsp3v2.bsp file.
Download visbjp.zip and extract it. Run
Bspinfo.exe -prt gmsp3v2.bsp
This is important: Between each Vis tool you have to restore the original gmsp3v2.bsp file. To do that remove the generated gmsp3v2.bsp file and recreated it by making a copy of the copy you made earlier. If you do not do this, funky errors will happen.
Download wvis_20100119.7z and extract it. Run
WVis.exe gmsp3v2.bsp
Download tyrutils-0.5-win32.zip and extract it. Here you find vis.exe in the bin/ directory. Run
vis.exe gmsp3v2.bsp
If you are on Linux, use tyrutils-0.5.tar.gz . Just make
, it will build a binary named vis in the bin/ directory.
Download quakeforge-tools-0.7.2-win32.zip and extract it. Here you find qfvis.exe in the quakeforge-0.7.2-win32/bin/ directory. Run
qfvis.exe -t 4 gmsp3v2.bsp
Adjust the number after the -t according the number of threads your machine can run in parallel.
And for laughs and nostalgia also run a full-vis with the one single-threaded Vis.exe from the bjp tools.
Vis.exe gmsp3v2.bsp
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 | qfvis | bjp's Vis | Name |
---|---|---|---|---|---|---|
i5-3470 | Linux/Wine | 13min | 67s | Spirit | ||
Intel(R) Atom(TM) CPU N570 @ 1.66GHz | Linux | 1182s | Spirit |