All of lore.kernel.org
 help / color / mirror / Atom feed
* An apparent large performance regression of 3D display over the network
@ 2011-01-19  9:01 Alan W. Irwin
  2011-01-25 20:46 ` Alan W. Irwin
                   ` (2 more replies)
  0 siblings, 3 replies; 6+ messages in thread
From: Alan W. Irwin @ 2011-01-19  9:01 UTC (permalink / raw)
  To: intel-gfx

Three years ago on a Debian testing system that was to become Debian
lenny, I made a test of running low-end 3D games (tuxracer and
foobillard) on a remote box on my 100Mbit LAN while displaying them on
my local Debian testing box X server with g33 chipset.  The games were
quite playable (in fact indistinguishable from playing the games
locally if I recall correctly).

Fast forward to today, when I once again tried the foobillard part of
the test (I didn't bother with tuxracer) with the same local (g33)
hardware but this time with Debian testing (squeeze) installed on that
locally displaying box.  foobillard has become completely unplayable
over the network with the former smooth movement reduced to what looks
like a series of snapshots with large gaps in between.  The LAN
network I have now is 1 gigabit as opposed to the older 100Megabit LAN
network I had when the remote 3D games worked well.  I can play
foobillard and tuxracer just fine locally on that machine so it
appears local 3D is in reasonable shape.

foobillard and tuxracer are just subjective tests of whether 3D
rendering works reasonably efficiently over the network, but my
impression is the regression in that regard is at least one or two
orders of magnitude in speed in order to reduce smooth effects to a
series of snapshots.  Thus, objective tests of remote 3D efficiency of
the old Intel stack from three years ago versus the current one should
pick up this performance regression easily.

I recently bought another computer (ASUS Eee Box with 945GME chipset)
that shows foobillard is unplayable over the network in the same way
while local running of that game is fine on that box.  I have now
configured that box to be an X-terminal (a configuration I far prefer
because it reduces sysadmin issues a lot).  The 2D KDE desktop
displays well for that configuration, but I have extreme doubts
(haven't tried them yet) about whether remote 3D desktop effects will
work at all considering this huge slowdown I get with remote running
of foobillard over the local 1 Gigabit LAN with that X-terminal.

One possibility is there may be something extra I have to do now to
make remote 3D display efficient over an ssh connection.  Advice in
that regard would be helpful.  (Currently, I just set ForwardX11 yes
and ForwardAgent yes for the host in question in .ssh/config for
the local computer.)

But if ssh configuration is not the issue, then it appears there has
been an efficiency regression for remote 3D at least for the 945GME
(GMA 950) and g33 (GMA 3100) chipsets. Has anyone here found
foobillard or similar low-end 3D games to be playable or 3D desktop
effects to work reasonably efficiently over fast LAN networks with
today's Intel graphics driver?

Of course, if this really turns out to be a general regression in
remote 3D display efficiency, then that regression obviously
corresponds with the X stack reorganization by Intel that has occurred
over the last 3 years. I expect making local 3D display efficient for
that newly organized stack is still one of the top priorities for
Intel developers, but I hope dealing with this efficiency regression
for remote 3D (if that is what it is) is at least on the agenda. After
all, with 3D desktop effects becoming more and more important and with
low-end 3D games as a "would be nice", reasonably efficient X network
transparency for 3D display is an important issue for those using X
terminals.

Let me know if there are more quantitative tests of efficiency you
would like me to run between local and remote display of 3D on either
the 945GME or g33 boxes.

Alan
__________________________
Alan W. Irwin

Astronomical research affiliation with Department of Physics and Astronomy,
University of Victoria (astrowww.phys.uvic.ca).

Programming affiliations with the FreeEOS equation-of-state implementation
for stellar interiors (freeeos.sf.net); PLplot scientific plotting software
package (plplot.org); the libLASi project (unifont.org/lasi); the Loads of
Linux Links project (loll.sf.net); and the Linux Brochure Project
(lbproject.sf.net).
__________________________

Linux-powered Science
__________________________

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: An apparent large performance regression of 3D display over the network
  2011-01-19  9:01 An apparent large performance regression of 3D display over the network Alan W. Irwin
@ 2011-01-25 20:46 ` Alan W. Irwin
  2011-01-25 23:18 ` Sven Arvidsson
  2011-02-14 14:34 ` Sven Arvidsson
  2 siblings, 0 replies; 6+ messages in thread
From: Alan W. Irwin @ 2011-01-25 20:46 UTC (permalink / raw)
  To: intel-gfx

I would really appreciate on of the Intel developers taking a quick
shot at answering these general question.  To summarize: do you
confirm bad results (typically 1 frame per second) for running remote
3D apps over the network while displaying them locally?  If so, is a
fix for this performance regression relative to the X Intel stack of
several years ago on the agenda?

On 2011-01-19 01:01-0800 Alan W. Irwin wrote:

> Three years ago on a Debian testing system that was to become Debian
> lenny, I made a test of running low-end 3D games (tuxracer and
> foobillard) on a remote box on my 100Mbit LAN while displaying them on
> my local Debian testing box X server with g33 chipset.  The games were
> quite playable (in fact indistinguishable from playing the games
> locally if I recall correctly).
>
> Fast forward to today, when I once again tried the foobillard part of
> the test (I didn't bother with tuxracer) with the same local (g33)
> hardware but this time with Debian testing (squeeze) installed on that
> locally displaying box.  foobillard has become completely unplayable
> over the network with the former smooth movement reduced to what looks
> like a series of snapshots with large gaps in between.  The LAN
> network I have now is 1 gigabit as opposed to the older 100Megabit LAN
> network I had when the remote 3D games worked well.  I can play
> foobillard and tuxracer just fine locally on that machine so it
> appears local 3D is in reasonable shape.
>
> foobillard and tuxracer are just subjective tests of whether 3D
> rendering works reasonably efficiently over the network, but my
> impression is the regression in that regard is at least one or two
> orders of magnitude in speed in order to reduce smooth effects to a
> series of snapshots.  Thus, objective tests of remote 3D efficiency of
> the old Intel stack from three years ago versus the current one should
> pick up this performance regression easily.
>
> I recently bought another computer (ASUS Eee Box with 945GME chipset)
> that shows foobillard is unplayable over the network in the same way
> while local running of that game is fine on that box.  I have now
> configured that box to be an X-terminal (a configuration I far prefer
> because it reduces sysadmin issues a lot).  The 2D KDE desktop
> displays well for that configuration, but I have extreme doubts
> (haven't tried them yet) about whether remote 3D desktop effects will
> work at all considering this huge slowdown I get with remote running
> of foobillard over the local 1 Gigabit LAN with that X-terminal.
>
> One possibility is there may be something extra I have to do now to
> make remote 3D display efficient over an ssh connection.  Advice in
> that regard would be helpful.  (Currently, I just set ForwardX11 yes
> and ForwardAgent yes for the host in question in .ssh/config for
> the local computer.)
>
> But if ssh configuration is not the issue, then it appears there has
> been an efficiency regression for remote 3D at least for the 945GME
> (GMA 950) and g33 (GMA 3100) chipsets. Has anyone here found
> foobillard or similar low-end 3D games to be playable or 3D desktop
> effects to work reasonably efficiently over fast LAN networks with
> today's Intel graphics driver?
>
> Of course, if this really turns out to be a general regression in
> remote 3D display efficiency, then that regression obviously
> corresponds with the X stack reorganization by Intel that has occurred
> over the last 3 years. I expect making local 3D display efficient for
> that newly organized stack is still one of the top priorities for
> Intel developers, but I hope dealing with this efficiency regression
> for remote 3D (if that is what it is) is at least on the agenda. After
> all, with 3D desktop effects becoming more and more important and with
> low-end 3D games as a "would be nice", reasonably efficient X network
> transparency for 3D display is an important issue for those using X
> terminals.
>
> Let me know if there are more quantitative tests of efficiency you
> would like me to run between local and remote display of 3D on either
> the 945GME or g33 boxes.
>
> Alan
> __________________________
> Alan W. Irwin
>
> Astronomical research affiliation with Department of Physics and Astronomy,
> University of Victoria (astrowww.phys.uvic.ca).
>
> Programming affiliations with the FreeEOS equation-of-state implementation
> for stellar interiors (freeeos.sf.net); PLplot scientific plotting software
> package (plplot.org); the libLASi project (unifont.org/lasi); the Loads of
> Linux Links project (loll.sf.net); and the Linux Brochure Project
> (lbproject.sf.net).
> __________________________
>
> Linux-powered Science
> __________________________
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/intel-gfx
>

__________________________
Alan W. Irwin

Astronomical research affiliation with Department of Physics and Astronomy,
University of Victoria (astrowww.phys.uvic.ca).

Programming affiliations with the FreeEOS equation-of-state implementation
for stellar interiors (freeeos.sf.net); PLplot scientific plotting software
package (plplot.org); the libLASi project (unifont.org/lasi); the Loads of
Linux Links project (loll.sf.net); and the Linux Brochure Project
(lbproject.sf.net).
__________________________

Linux-powered Science
__________________________

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: An apparent large performance regression of 3D display over the network
  2011-01-19  9:01 An apparent large performance regression of 3D display over the network Alan W. Irwin
  2011-01-25 20:46 ` Alan W. Irwin
@ 2011-01-25 23:18 ` Sven Arvidsson
  2011-01-28  0:15   ` Alan W. Irwin
  2011-02-14 14:34 ` Sven Arvidsson
  2 siblings, 1 reply; 6+ messages in thread
From: Sven Arvidsson @ 2011-01-25 23:18 UTC (permalink / raw)
  To: intel-gfx


[-- Attachment #1.1: Type: text/plain, Size: 749 bytes --]

I think that you're supposed to set LIBGL_ALWAYS_INDIRECT=true (on the
client, the one running the X server) otherwise you'll end up with
software rendering. 

You can check if you're getting software rendering or not with "glxinfo
| grep renderer"

But on my system I can't seem to get this to work, I'll either end up
using the clients or the servers' software renderer...

Given that this problem isn't Intel-specific it's probably a better idea
to move the discussion to the xorg list <xorg@lists.freedesktop.org>
and/or file bugs on https://bugs.freedesktop.org


And just for clarity, I'm neither an Intel employee or an X dev - just
another user :) 

-- 
Cheers,
Sven Arvidsson
http://www.whiz.se
PGP Key ID 760BDD22


[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: An apparent large performance regression of 3D display over the network
  2011-01-25 23:18 ` Sven Arvidsson
@ 2011-01-28  0:15   ` Alan W. Irwin
  0 siblings, 0 replies; 6+ messages in thread
From: Alan W. Irwin @ 2011-01-28  0:15 UTC (permalink / raw)
  To: Sven Arvidsson; +Cc: intel-gfx

> I think that you're supposed to set LIBGL_ALWAYS_INDIRECT=true (on the
client, the one running the X server) otherwise you'll end up with
software rendering.

> You can check if you're getting software rendering or not with "glxinfo
| grep renderer"

> But on my system I can't seem to get this to work, I'll either end up
using the clients or the servers' software renderer...

A huge thanks to you for this key LIBGL_ALWAYS_INDIRECT suggestion!  I
cannot find a man page where LIBGL_ALWAYS_INDIRECT is documented.  I
looked specifically for this in the Xorg, xorg.conf, intel, and even
radeon man page, and also using a google search for a man page
reference.  That google search did find some non-man documentation
that indicated the value should be "1" rather than "true" which
explains why it is not working for you.

Here are some interesting LIBGL_ALWAYS_INDIRECT results on the (g33)
raven machine (where the X clients like foobillard are located) from
my 945GME X-terminal where the X server is running.

When LIBGL_ALWAYS_INDIRECT is not set, I get the following results:

irwin@raven> glxinfo |grep render
direct rendering: Yes
OpenGL renderer string: Software Rasterizer

So it was that Software Rasterizer that was killing the speed of
foobillard.

When LIBGL_ALWAYS_INDIRECT is set to 1, I get very different results.

irwin@raven> export LIBGL_ALWAYS_INDIRECT=1
irwin@raven> glxinfo |grep render
direct rendering: No (LIBGL_ALWAYS_INDIRECT set)
OpenGL renderer string: Mesa DRI Intel(R) 945GME GEM 20091221 2009Q4
x86/MMX/SSE2

That clearly identifies the 945GME (where the X server is located in
this case) as where OpenGL rendering will be done, and indeed with
LIBGL_ALWAYS_INDIRECT=1, foobillard is playable via my X-terminal!  So
thanks again for directing me to this solution.

I don't think I had to set this environment variable for my
corresponding tests several years ago, but I may just not be
remembering properly.  However, clearly it is necessary now, and I
wish that environment variable was better documented.

I have asked this question a number of places (including lxer.com and
Dave Richards's blog where he is the guy who is managing ~500 thin
Linux clients for the City of Largo, Florida) where I expected someone
would have the answer. But nobody did (the general ignorance of X
networking transparency by veteran Linux users is frightening) until
you came through. You have made my day.

> [...]And just for clarity, I'm neither an Intel employee or an X dev - just
another user :)

That's allowed and even encouraged.  :-) This list was started as a
list for the Intel X community of users and developers which is why I
joined it at its inception as a user.  It is great to get fundamental
help here like this from another user.

I hate to end on a negative note, but I have also tried etracer
(extreme tuxracer) with LIBGL_ALWAYS_INDIRECT=1, and it is not
playable (difficulties even using the mouse-driven menus) from my
X-terminal even though it can be run directly without issues.  So
there is clearly still a performance regression of 3D display over the
network (assuming etracer is not that different from tuxracer)
compared to the classic X intel stack that I used for my tuxracer
tests several years ago, but it is not as extreme (since at least
foobillard works smoothly with LIBGL_ALWAYS_INDIRECT=1) as I first
reported.  Nevertheless, I am still hoping for an answer from the
Intel developers on whether improving the efficiency of 3D display
over the network is at least on their agenda.

Alan
__________________________
Alan W. Irwin

Astronomical research affiliation with Department of Physics and Astronomy,
University of Victoria (astrowww.phys.uvic.ca).

Programming affiliations with the FreeEOS equation-of-state implementation
for stellar interiors (freeeos.sf.net); PLplot scientific plotting software
package (plplot.org); the libLASi project (unifont.org/lasi); the Loads of
Linux Links project (loll.sf.net); and the Linux Brochure Project
(lbproject.sf.net).
__________________________

Linux-powered Science
__________________________

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: An apparent large performance regression of 3D display over the network
  2011-01-19  9:01 An apparent large performance regression of 3D display over the network Alan W. Irwin
  2011-01-25 20:46 ` Alan W. Irwin
  2011-01-25 23:18 ` Sven Arvidsson
@ 2011-02-14 14:34 ` Sven Arvidsson
  2011-02-14 16:52   ` Alan W. Irwin
  2 siblings, 1 reply; 6+ messages in thread
From: Sven Arvidsson @ 2011-02-14 14:34 UTC (permalink / raw)
  To: intel-gfx


[-- Attachment #1.1: Type: text/plain, Size: 291 bytes --]

Hi,

Not sure if you have seen this patch (I just stumbled upon it myself)
but it sounds like it makes quite a difference with indirect rendering:
http://lists.x.org/archives/xorg-devel/2011-January/018623.html

-- 
Cheers,
Sven Arvidsson
http://www.whiz.se
PGP Key ID 760BDD22


[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: An apparent large performance regression of 3D display over the network
  2011-02-14 14:34 ` Sven Arvidsson
@ 2011-02-14 16:52   ` Alan W. Irwin
  0 siblings, 0 replies; 6+ messages in thread
From: Alan W. Irwin @ 2011-02-14 16:52 UTC (permalink / raw)
  To: Sven Arvidsson; +Cc: intel-gfx

On 2011-02-14 15:34+0100 Sven Arvidsson wrote:

> Hi,
>
> Not sure if you have seen this patch (I just stumbled upon it myself)
> but it sounds like it makes quite a difference with indirect rendering:
> http://lists.x.org/archives/xorg-devel/2011-January/018623.html

Yes, I noticed that patch from Chris Wilson as well and look forward
to when it is propagated to Debian.

Chris, does that patch make the etracer initial menu usable with

export LIBGL_ALWAYS_INDIRECT=1

? That menu is almost unusable (much flickering, extremely slow
response to cursor motions) here for LIBGL_ALWAYS_INDIRECT=1.  That's
for the case of running etracer directly on the machine where the X
server is located.  For those same conditions with
LIBGL_ALWAYS_INDIRECT not set, the etracer initial menu is fine.

As an X-terminal user for the last decade, I am glad to see that there
is at least some attention being paid to efficiency issues with the
LIBGL_ALWAYS_INDIRECT=1 case.

Alan
__________________________
Alan W. Irwin

Astronomical research affiliation with Department of Physics and Astronomy,
University of Victoria (astrowww.phys.uvic.ca).

Programming affiliations with the FreeEOS equation-of-state implementation
for stellar interiors (freeeos.sf.net); PLplot scientific plotting software
package (plplot.org); the libLASi project (unifont.org/lasi); the Loads of
Linux Links project (loll.sf.net); and the Linux Brochure Project
(lbproject.sf.net).
__________________________

Linux-powered Science
__________________________

^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2011-02-14 16:52 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2011-01-19  9:01 An apparent large performance regression of 3D display over the network Alan W. Irwin
2011-01-25 20:46 ` Alan W. Irwin
2011-01-25 23:18 ` Sven Arvidsson
2011-01-28  0:15   ` Alan W. Irwin
2011-02-14 14:34 ` Sven Arvidsson
2011-02-14 16:52   ` Alan W. Irwin

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.