[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: nvidia vs ati



On Sun, Nov 30, 2003 at 10:12:07AM +0100, Elie De Brauwer wrote:
> Let's do some benchmarking 
> I have a PIV 2.8 ghz (800 mhz fsb), 1 gig ddr 400 ram and an geforce fx 5900 
> ultra with 256 meg ram. When running X at 1600x1200 resolution I get about 
> 4800 fps in glxgears

Ok, you are making me feel bad.

I've got an XP 1800+ on a MSI K7T266 board with a matrox G550 AGP
running in 1280x960 and X 4.3.0.1.  Noramlly run dual head xinerama but
this is running with one screen setup:

My fps is not quite so impressive as others have posted.  Before I loaded
my agpgart module I had:

$ glxgears

960 frames in 5.0 seconds = 192.000 FPS
960 frames in 5.0 seconds = 192.000 FPS
960 frames in 5.0 seconds = 192.000 FPS
916 frames in 5.0 seconds = 183.200 FPS

After insmod agpgart

1334 frames in 5.0 seconds = 266.800 FPS
1556 frames in 5.0 seconds = 311.200 FPS
1557 frames in 5.0 seconds = 311.400 FPS
1557 frames in 5.0 seconds = 311.400 FPS

Which is still less than exciting.  And that's the default window size
for glxgears.  Full screen (maximized) is real ugly:

164 frames in 5.0 seconds = 32.800 FPS
165 frames in 5.0 seconds = 33.000 FPS
164 frames in 5.0 seconds = 32.800 FPS

So is that just old, slow hardware[1], or should I be looking at other
possible problems?


Nothing jumps out in the logs:

moseley@bumby:~$ egrep '(\(EE\)|\(WW\))' /var/log/XFree86.0.log
         (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(WW) Open APM failed (/dev/apm_bios) (No such file or directory)
(WW) Warning, couldn't open module mga_hal
(EE) MGA: Failed to load module "mga_hal" (module does not exist, 0)
(WW) MGA(0): Video BIOS info block not detected!


moseley@bumby:~$ fgrep -i agp  /var/log/XFree86.0.log
(--) PCI:*(1:0:0) Matrox Graphics, Inc. MGA G550 AGP rev 1, Mem @ 0xdc000000/25, 0xdfefc000/14, 0xdf000000/23, BIOS @ 0xdfec0000/17
        mga2164w AGP, mgag100, mgag100 PCI, mgag200, mgag200 PCI, mgag400,
(**) MGA(0): Option "AGPMode" "4"
(**) MGA(0): Using AGP 4x mode
(II) MGA(0): [agp] Mode 0x1f000207 [AGP 0x1106/0x3099; Card 0x102b/0x2527]
(II) MGA(0): [agp] 12288 kB allocated with handle 0xfb520000
(II) MGA(0): [agp] WARP microcode handle = 0xe0000000
(II) MGA(0): [agp] WARP microcode mapped at 0x42a15000
(II) MGA(0): [agp] Primary DMA handle = 0xe0008000
(II) MGA(0): [agp] Primary DMA mapped at 0x42a1d000
(II) MGA(0): [agp] DMA buffers handle = 0xe0108000
(II) MGA(0): [agp] DMA buffers mapped at 0x42b1d000
(II) MGA(0): [agp] agpTexture handle = 0xe0908000
(II) MGA(0): [agp] agpTexture size: 2816 kb
(II) MGA(0): [agp] Status page mapped at 0x4001e000

[1] BTW -- I used to run swish-e indexing on this machine and it would
index 25,000 files in about a minute.  A few OS changes later, hard disk
upgrades, and another 1/4 of RAM and now it indexes those same files in
about 4 minutes.  So maybe something else is going on, but I don't know
where to start looking.  Any ideas?

Thanks,


-- 
Bill Moseley
moseley@hank.org



Reply to: