From: Marcin Romaszewicz (marcin++at++asmodean.engr.sgi.com)
Date: 01/25/2000 10:30:05
On Tue, 25 Jan 2000, Harry Overs wrote:
> I am currently experimenting with Performer 2.3, LInux and DRI with the Voodoo3.
> We have a large terrain and running a single 640,480 channel on a PII450, I am seeing 100% CPU utilisation using perfly.
> However, the stats are showing
> app 1.6 cull 0.1 draw 9.0 but the frame-rate is only 30hz.
>
> This is with a FOV of 6000. Any higher and the frame rate drops dramatically.
6000? That can't be. You mean 60 degrees, right? As you increase the
FOV further, you bring more objects into view, which will take more time
to render.
>
>
> Does this indicate a CPU bottleneck ?
>
Probably. Run in a smaller window, if the program does not run faster,
then you are most likely CPU (geometry) limited. If it does run faster,
you are fill limited, but I suspect that's not the case.
>
> Or are we seeing 100% CPU because the CPU is busy waiting for something else ?
>
The Voodoo cards do not have geometry acceleration, so your CPU is busy
transforming all vertices through modleview, computing lighting,
etc. For this reason, most PC 3D cards are heavily geometry limited.
-- Marcin
This archive was generated by hypermail 2b29 : Tue Jan 25 2000 - 10:30:19 PST