tl;dr I just landed a change that may improve drawing performance. Because the code path depends on the machine, it is difficult to test that I didn't break anything. Please let me know if you notice a drawing speed difference in Chrome builds after r35390/35392 (latter was a build fix for the former).
Details: Previously we had two paths for drawing: 1) via shared memory pixmaps: image data -> shared memory -> copied to backing store by X server 2) slow fallback case: image data -> XImage -> serialized to X server pixmap -> copied to backing store by X server It turns out the first one has relatively weak support on existing machines. I just added one in the middle, for when the first one isn't supported: 1.5) shared memory putimage: image data -> XImage -> shared memory -> copied to pixmap by X server -> copied to backing store by X server It seems this is likely the code path that will run on most machines, and it saves a couple of serialization/copy steps, so hopefully it'll be faster. If you were to notice it you would notice it on drawing-heavy pages, like a canvas demo or some instances of Flash. -- Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev
