← Back to team overview

hybrid-graphics-linux team mailing list archive

Fwd: [Bug 27618] Very slow wine Opengl performance with ASUS 1215N

 

Well, they basically said it's "normal" to be slow.. however that can be.. :(
-turgut


-------- Original Message --------
Subject: 	[Bug 27618] Very slow wine Opengl performance with ASUS 1215N
Date: 	Mon, 27 Jun 2011 13:24:00 -0500
From: 	wine-bugs@xxxxxxxxxx
To: 	turgut@xxxxxxxxxxxxx



http://bugs.winehq.org/show_bug.cgi?id=27618

Roderick Colenbrander<thunderbird2k@xxxxxxxxx>  changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
                 CC|                            |thunderbird2k@xxxxxxxxx
         Resolution|                            |INVALID

--- Comment #1 from Roderick Colenbrander<thunderbird2k@xxxxxxxxx>  2011-06-27 13:23:59 CDT ---
The issue you are seeing is not a Wine problem. Bumblebee uses VirtualGL and
the use of VirtualGL comes at an additional performance hit.

The way things work when you use VirtualGL is that all 3D content is rendered
on the Nvidia GPU. In order to show the images on your screen, every 3D frame
has to copied back to system memory and copied back to video memory on your
Intel card.
This is quite slow and stress the PCI-E bus quite a bit (especially on laptops
where you typically have much less bandwidth). It directly slows down the game
as well because this is all happening during the 'glXSwapBuffers' call the game
makes.

On Windows the Nvidia drivers use similar VirtualGL-like tricks to render on
the Intel GPU, but there are a lot more optimizations are in place (and there
is likely more direct interaction with the Intel driver).

At least this issue is definitely not a Wine bug.

--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You reported the bug.



Follow ups