VOGONS


First post, by p6889k

User metadata
Rank Member
Rank
Member

Finally was able to add Voodoo 2 to my system and decided to benchmark with Quake 2. Can anyone comment on whether these results are about what I should expect or are there config changes I should try to improve performance:

HW: Pentium Pro 200Mhz/512kb cache, 256MB RAM, Millennium 2 8MB, 2x STB Voodoo 2 12MB, AWE64 Gold
SW: NT4 SP6, Quake 2 v.3.20, Voodoo NT Driver v3.02.02

demo1.dm2
640x480: 46.0 fps
800x600: 39.9 fps
SLI 800x600: 46.6 fps
SLI 1024x768: 42.6 fps

Changing Vsync on/off didn't make any difference.
Changing 8-bit textures on/off didn't make any difference.

crusher.dm2
640x480: 21.1 fps
800x600: 20.5 fps
SLI 800x600: 21.6 fps
SLI 1024x768: 20.9 fps

Changing Vsync on/off didn't make any difference.
Changing 8-bit textures on/off didn't make any difference.

Sinclair ZX Spectrum 48k, 48k+, 128k, +2
Amiga 1200, 68030/40mhz
386DX/33, ET4000, SBPro2, MT32
Dual PPro/200, Millennium II, Voodoo 2, AWE32, SC-55
etc.

Reply 2 of 14, by p6889k

User metadata
Rank Member
Rank
Member
The Serpent Rider wrote on 2020-12-19, 14:00:

How much without sound?

demo1.dm2
640x480: 46.0 fps
800x600: 39.9 fps
SLI 640x480: 46.1 fps
SLI 800x600: 46.6 fps
SLI 1024x768: 42.6 fps
SLI 640x480, nosound: 48.1 fps
SLI 800x600:, nosound 48 fps
SLI 1024x768, nosound: 43.5 fps

Changing Vsync on/off didn't make any difference.
Changing 8-bit textures on/off didn't make any difference.

crusher.dm2
640x480: 21.1 fps
800x600: 20.5 fps
SLI 640x480: 21.0 fps
SLI 800x600: 21.6 fps
SLI 1024x768: 20.9 fps
SLI 640x480, nosound: 22.5 fps
SLI 800x600:, nosound 22 fps
SLI 1024x768, nosound: 22.2 fps

Changing Vsync on/off didn't make any difference.
Changing 8-bit textures on/off didn't make any difference.

Last edited by p6889k on 2020-12-19, 18:04. Edited 5 times in total.

Sinclair ZX Spectrum 48k, 48k+, 128k, +2
Amiga 1200, 68030/40mhz
386DX/33, ET4000, SBPro2, MT32
Dual PPro/200, Millennium II, Voodoo 2, AWE32, SC-55
etc.

Reply 3 of 14, by The Serpent Rider

User metadata
Rank l33t++
Rank
l33t++

Yep, more or less right.
Re: Graphics card for Pentium Pro build

I must be some kind of standard: the anonymous gangbanger of the 21st century.

Reply 4 of 14, by bloodem

User metadata
Rank Oldbie
Rank
Oldbie

Interesting... My overclocked Pentium MMX233 @ 266 MHz with a Voodoo Banshee gets pretty close to these results (with sound, I got 45 FPS in Quake 2 demo1.dm2 and 87 FPS in GLQuake).
I would have expected the Pentium Pro to be much faster in Quake 2.

1 x PLCC-68 / 2 x PGA132 / 5 x Skt 3 / 9 x Skt 7 / 12 x SS7 / 1 x Skt 8 / 14 x Slot 1 / 5 x Slot A
5 x Skt 370 / 8 x Skt A / 2 x Skt 478 / 2 x Skt 754 / 3 x Skt 939 / 7 x LGA775 / 1 x LGA1155
Current PC: Ryzen 7 5800X3D
Backup PC: Core i7 7700k

Reply 5 of 14, by The Serpent Rider

User metadata
Rank l33t++
Rank
l33t++

Quake 2 is sensitive to I/O bus speed. In MDK2, equally clocked Pentium Pro is 40% faster.

I must be some kind of standard: the anonymous gangbanger of the 21st century.

Reply 7 of 14, by The Serpent Rider

User metadata
Rank l33t++
Rank
l33t++

You don't need to overclock FSB. Most if not all boards had 3.5x multiplier and Pentium Pro is unlocked.

I must be some kind of standard: the anonymous gangbanger of the 21st century.

Reply 8 of 14, by p6889k

User metadata
Rank Member
Rank
Member

I overclocked to 233MHz by setting the multipler to 3.5. Here are some results. Only very minor gains. Game also crashed once, probably due to the overclock, I didn't increase voltage. I'm going to set it back to 200MHz, this overclock was just to see if/how it works, don't really need it at 233Mhz. Also, didn't test SLI this time as I already removed the 2nd Voodoo from the PC - it's going to another PC.

demo1.dm2
640x480, software rendering: 12.3 fps
800x600, software rendering: 9.3 fps
640x480, CPU at 233Mhz, software rendering: 13.6 fps
800x600, CPU at 233Mhz, software rendering: 10.1 fps
640x480: 46.0 fps
800x600: 39.9 fps
640x480, CPU at 233Mhz: 48.9 fps
800x600, CPU at 233Mhz: 41.4 fps
640x480, CPU at 233Mhz, nosound: 50.7 fps
800x600, CPU at 233Mhz, nosound: 42.5 fps
SLI 640x480: 46.1 fps
SLI 800x600: 46.6 fps
SLI 1024x768: 42.6 fps
SLI 640x480, nosound: 48.1 fps
SLI 800x600:, nosound 48 fps
SLI 1024x768, nosound: 43.5 fps

crusher.dm2
640x480: 21.1 fps
800x600: 20.5 fps
640x480, CPU at 233Mhz: 22.7 fps
800x600, CPU at 233Mhz: 22.3 fps
640x480, CPU at 233Mhz, nosound: 25.0 fps
800x600, CPU at 233Mhz, nosound: 23.6 fps
SLI 640x480: 21.0 fps
SLI 800x600: 21.6 fps
SLI 1024x768: 20.9 fps
SLI 640x480, nosound: 22.5 fps
SLI 800x600:, nosound 22 fps
SLI 1024x768, nosound: 22.2 fps

Sinclair ZX Spectrum 48k, 48k+, 128k, +2
Amiga 1200, 68030/40mhz
386DX/33, ET4000, SBPro2, MT32
Dual PPro/200, Millennium II, Voodoo 2, AWE32, SC-55
etc.

Reply 9 of 14, by p6889k

User metadata
Rank Member
Rank
Member

Also found this great article from Phil on Voodoo 2 scaling where he compares large variety of CPUs: https://www.philscomputerlab.com/voodoo-2-and … ng-project.html

Looking at it, my numbers seem to be in the ballpark with MMX233 CPU in single card config and significantly higher in SLI. E.g. here are some from Phil's tests for Quake 2 timedemo.

800x600, P200: 29.5
800x600, MMX200: 36.6
800x600, MMX233: 39.9
Mine were 39.9 at PPro 200Mhz and 41.4 at PPro 233Mhz

800x600 SLI, P200: 29.5
800x600 SLI, MMX200: 36.8
800x600 SLI, MMX233: 40.4
Mine were 46.6 at PPro 200Mhz

Sinclair ZX Spectrum 48k, 48k+, 128k, +2
Amiga 1200, 68030/40mhz
386DX/33, ET4000, SBPro2, MT32
Dual PPro/200, Millennium II, Voodoo 2, AWE32, SC-55
etc.

Reply 10 of 14, by rmay635703

User metadata
Rank Oldbie
Rank
Oldbie

The reason I mention 225mhz was because I never had luck overclocking 512kb ppros any faster than that.

Also Q2 would run a lot faster at 75x3 than 66x3.5

My single chip boards all had 75mhz FSB and most of my ppro 180’s would OC to 233.

My guess is that Intel could have sold ppro233’s if they only offered it in 256kb varieties, the bigger cache modules likely couldn’t clock any higher than 200

Reply 11 of 14, by p6889k

User metadata
Rank Member
Rank
Member
rmay635703 wrote on 2020-12-20, 17:39:
The reason I mention 225mhz was because I never had luck overclocking 512kb ppros any faster than that. […]
Show full quote

The reason I mention 225mhz was because I never had luck overclocking 512kb ppros any faster than that.

Also Q2 would run a lot faster at 75x3 than 66x3.5

My single chip boards all had 75mhz FSB and most of my ppro 180’s would OC to 233.

My guess is that Intel could have sold ppro233’s if they only offered it in 256kb varieties, the bigger cache modules likely couldn’t clock any higher than 200

Interesting, would like to try the 75fsb but I don't think my Intel VS440FX motherboard supports it.

Sinclair ZX Spectrum 48k, 48k+, 128k, +2
Amiga 1200, 68030/40mhz
386DX/33, ET4000, SBPro2, MT32
Dual PPro/200, Millennium II, Voodoo 2, AWE32, SC-55
etc.

Reply 12 of 14, by The Serpent Rider

User metadata
Rank l33t++
Rank
l33t++

My guess is that Intel could have sold ppro233’s if they only offered it in 256kb varieties, the bigger cache modules likely couldn’t clock any higher than 200

Not really. They just didn't had enough headroom, so to speak, to make 233 Mhz models. Shipping a CPU which edges on maximum stable clocks as stock speed could potentially lead to a disaster. Due to variables like quality of VRM, ambient temperature and cooling.

I must be some kind of standard: the anonymous gangbanger of the 21st century.

Reply 13 of 14, by rmay635703

User metadata
Rank Oldbie
Rank
Oldbie
The Serpent Rider wrote on 2020-12-23, 17:03:

My guess is that Intel could have sold ppro233’s if they only offered it in 256kb varieties, the bigger cache modules likely couldn’t clock any higher than 200

Not really. They just didn't had enough headroom, so to speak, to make 233 Mhz models. Shipping a CPU which edges on maximum stable clocks as stock speed could potentially lead to a disaster. Due to variables like quality of VRM, ambient temperature and cooling.

Why then did all 2 dozen of my 256k PPROs all OC above 200mhz (all rated 180mhz) but only half the 512kb units OC at all and if they do OC never more than 225?
One of the 180’s would go faster than 233mhz and ran stable in XP.
(I never touched voltage or cooling, got many years under Windows 2000 out of the old Omnitech workstations)

From what I remember the 256k unit cache all were “old process” and the 512kb units were new but despite this the 512k units are nearly impossible to overclock, yet the old 256k units all were excellent overclockers, even the single 150 I had would run 200mhz.

Ah well

Reply 14 of 14, by Spitz

User metadata
Rank Member
Rank
Member
rmay635703 wrote on 2020-12-24, 21:16:
Why then did all 2 dozen of my 256k PPROs all OC above 200mhz (all rated 180mhz) but only half the 512kb units OC at all and if […]
Show full quote
The Serpent Rider wrote on 2020-12-23, 17:03:

My guess is that Intel could have sold ppro233’s if they only offered it in 256kb varieties, the bigger cache modules likely couldn’t clock any higher than 200

Not really. They just didn't had enough headroom, so to speak, to make 233 Mhz models. Shipping a CPU which edges on maximum stable clocks as stock speed could potentially lead to a disaster. Due to variables like quality of VRM, ambient temperature and cooling.

Why then did all 2 dozen of my 256k PPROs all OC above 200mhz (all rated 180mhz) but only half the 512kb units OC at all and if they do OC never more than 225?
One of the 180’s would go faster than 233mhz and ran stable in XP.
(I never touched voltage or cooling, got many years under Windows 2000 out of the old Omnitech workstations)

From what I remember the 256k unit cache all were “old process” and the 512kb units were new but despite this the 512k units are nearly impossible to overclock, yet the old 256k units all were excellent overclockers, even the single 150 I had would run 200mhz.

Ah well

Yep ... cruel situations. I do remember times where My P4 Prescott didn't wan't to overclock much, but Northwood with half of cache was more eager to overclock (we're talking about stability here...) ....

Well... I miss 80/90s ... End of story