[Spice-devel] Delay in Gimp when using qxl driver

[Alon Levy]

On Sun, Jan 22, 2012 at 03:18:14PM +0100, Dominique Rodrigues wrote:
> 
> Le 20/01/2012 20:04, Yaniv Kaul a écrit :
> >----- Original Message -----
> >>>samples    pcnt    function        DSO
> >>>
> >>>3796.00        60.4%    hashlittle
> >>This sucks, unfortunately I don't have any quick fix for it. It's the
> >>hash computation done on each image. Needless to say it needs to be
> >>optimized - either made more efficient or reduce the number of calls.
> >>
> >>Soren, FYI.
> >You could move to murmur2, like Windows' QXL driver (https://bugs.freedesktop.org/show_bug.cgi?id=37465) or murmur3 or other faster ones (https://bugs.freedesktop.org/show_bug.cgi?id=35775).
> >At least it's not hashed twice now(https://bugs.freedesktop.org/show_bug.cgi?id=37977 - worth updating bug status?!), but I'm not sure it should be hashed at all, if it's not cached.
> >Y.
> 
> That's true : when you draw in Gimp in a Windows Seven (64 bits)
> guest, you have absolutely no delay, at any speed.
> 
> Soren has recently improved a lot the qxl driver for Linux, but if
> you accelerate the mouvement of your mouse, the drawing can't still
> follow your mouse in Gimp.
> 
> I don't know why different functions have been choosen into the qxl
> drivers for Windows and Linux, but it could be interesting to
because it was done by different people at different times.

> benefit from the best of these different versions.
> 
> 
> Dominique Rodrigues

> begin:vcard
> fn:Dominique Rodrigues
> n:Rodrigues;Dominique
> org:nanoClouD
> adr:;;8, rue Lemercier;Paris;;75017;France
> email;internet:dominique.rodrigues at nanocloud.com
> title:Directeur Technique
> tel;work:+33 (0) 1 77 69 64 38
> tel;cell:+33 (0) 6 28 52 37 70
> url:www.nanocloud.com
> version:2.1
> end:vcard
>