<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - XWayland [weston 1.6.0] takes all CPU and is very slow on eee-pc" href="https://bugs.freedesktop.org/show_bug.cgi?id=86815#c11">Comment # 11</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - XWayland [weston 1.6.0] takes all CPU and is very slow on eee-pc" href="https://bugs.freedesktop.org/show_bug.cgi?id=86815">bug 86815</a> from <a class="email" href="mailto:zhigang.gong@gmail.com" title="Zhigang Gong <zhigang.gong@gmail.com>"> Zhigang Gong</a> <pre>(In reply to Pekka Paalanen from <a href="show_bug.cgi?id=86815#c10">comment #10</a>) > (In reply to Mildred Ki'Lya from <a href="show_bug.cgi?id=86815#c9">comment #9</a>) > > Sorry, I haven't been back on this for some time. I added the "-shm" option > > instead of removing it, and now xterms is as fast as it could be. That works. > > Okay, so the problem is triggered by Glamor, I believe. > > > The top symbols that are slowing things down are fetch_vector4, intel_idle, > > _mesa_execute_program and store_vector4 (the only above 5%). I'm guessing > > that there is non necessary memory copying that happens. Storing and > > fetching vectors uselessly, and waiting idely for the process to complete. > > Unfortunately that goes out of my personal expertise. > > Maybe the Intel GPU just does not have the hardware to do some thing and > therefore they are done on the CPU? You may be right here. This Eee PC is using pineview platform which doesn't have hardware vertex shader support. So all the vertex shader fallbacks to CPU side, it becomes extremly slow then. > Maybe the GL driver (in Mesa) is doing something unoptimal? > Or maybe Glamor is using GL in ways that cause the above? > Or could Glamor simply be a bad fit for this hardware and there should be > some automatic way to disable Glamor at runtime? > > I really don't know. > > If you need more weight to make a case, so that Intel/Glamor developers > would look into it, you could try running X.org with the modesetting DDX and > Glamor. That is, nothing Wayland nor Weston. If that has similar slowness, > you have a stronger case and could file it against Glamor or Intel. Whatever > solution comes from there should also apply to Xwayland.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>