Hi John,
I've had several suggestions (one off-list) to drop the nvidia driver
entirely, and it's working. My test steps have been to pop open Firefox,
send it to the Fantastic Contraption game (Flash, and heavy, but fun),
wiggle windows a bit, then open glxgears, wiggle it about, surf for a few
minutes, then maximize glxgears and minimize again.
With the nvidia driver glxgears was pretty fast, latencies were in the high
400k, once even up around 520k (ns). I've since tried the nv driver, and
glxgears is far slower, chugging away, and taking many seconds to maximize,
but the jitter topped off a little over 160k. I'm now trying the vesa
driver, and my worst after all of that is 33.5k. MUCH better, by an order of
magnitude from my first results. I hear that's still not great, but I'm sure
there's still more I can try, like disabling things.
Any suggestions for what I can turn off to squeeze more k's off my max
numbers? I'm sure I'll have to research how to turn each off :)
Thanks!
-g
I had a few suggestions in
On Sat, Oct 4, 2008 at 8:04 AM, John Kasunich <[EMAIL PROTECTED]>wrote:
> Gary Fixler wrote:
> > I tried to send a message last night, but it never showed up on the list.
> I
> > have the worst time getting messages through.
> >
> > Basically, I'm on an aging Shuttle PC from 2002 with an Nvidia GeForce4
> Ti
> > 4600. When I start up latency-test, I'm in the single-digit thousands,
> like
> > 6500 or so. If I play around online with Flash things (e.g. the Fantastic
> > Contraption game) it jumps to about 35k(ns) for the base thread jitter.
> If I
> > open glxgears it usually bumps up to 150k+, and if I maximize it, it
> soars
> > to well over 350k, sometimes almost 400k. The machine does feel laggy -
> slow
> > window redraws when dragging windows - but I'm also used to a much faster
> > machine now.
>
> Severe latency problems when running GLXgears almost always points
> towards hardware graphics acceleration. Usually the video board
> manufacturer has a proprietary driver which either disables interrupts
> for long periods, or does bus mastering DMA, or something else that
> interferes with the computer doing realtime code.
>
> There are two solutions to that:
>
> 1) use an open-source driver, such as the generic vesa driver, which
> doesn't use hardware acceleration. Graphics will be slower, but
> realtime performance will improve
>
> 2) switch to a different, perhaps older, graphics card Many people have
> had success with various Matrox cards
>
> Regards,
>
> John Kasunich
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's
> challenge
> Build the coolest Linux based applications with Moblin SDK & win great
> prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> Emc-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/emc-users
>
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Emc-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/emc-users
