> I thought about it again and made a plot of the fps over the pixel
> clock. This indicates that the different performance is *only* related
> to the CRT refresh. This is the Octave code I used to 
> generate the plot:
> 
> modes=[125.00; 115.50;  69.65;  45.80;  57.75;  34.83];
> fps  =[155.20; 165.20; 209.60; 229.40; 218.00; 235.00];
> 
> data=[modes,fps];
> gplot data with lines
> 
> The plot is attached as eps.

In other words, the amount of pixeldata that your RAMDAC reads
from memory slows your GL rendering down. Natural, just to proof.

If you had changed the last but one with the last but two value,
then your eps would have looked nicer.

Anyways, the numerical sum of both values is at about 270-280 for
your setup, so you could assume edges like this:
- If turning off ramdac reading totally, then gearls will run with 280 fps.
- If you could bring up pixel clock to 280 then any rendering 
  (not only gears) will stop. (whilst the sync cyles a bit might get
trough.)

Regards Alex.


_______________________________________________
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel

Reply via email to