Reply 20 of 23, by noshutdown
wrote:So those are immediately kind of interesting, as the Voodoo2s aren't really showing the kind of scaling you might expect and the TNT2 actually loses some performance going to a lower resolution! That to me suggests something in the system is getting swamped by the graphics cards output and totally failing to cope with it.
CPU is running at 5.5 x 100 - I did a run of SuperPi and it took 5:35; seems reasonable?
I did initially ignore the lower performance as me overestimating how well these machines used to run, but there are plenty of benchmarks of Voodoo2s/TNT2s with K6-2/3 CPUs which indicate this performance really isn't what you'd expect.
your superpi time is normal, so the problem is not within the cpu-cache-ram subsystem. now there are a few things to check out:
1. use everest or sisoft to see your tnt2 running in agp or pci mode.
2. your nvidia driver version? anything newer than 30.82 is not recommended on socket7 platforms.
3. check out the options in video driver: turn on optimizations, and disable vsync(may need the "coolbits" registry).
4. do you use built-in demo1 or crusher demo for quake2 benchmarking? i got 68fps with geforce2ultra in crusher, so if you are getting 40 crusher fps with tnt2 its probably right, but 40fps in demo1 is too low.
5. benchmark with sound disabled, running with sound can slow down by a lot. to disable sound, enter:
s_initsound 0
snd_restart
6. about that agp-aperture size, my suggestion is 64mb, setting it too small can reduce performance.