[Webkit-unassigned] [Bug 29279] [Qt] Use RGB16 format for images on Symbian platform

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Wed Oct 14 19:09:38 PDT 2009


https://bugs.webkit.org/show_bug.cgi?id=29279





--- Comment #27 from Chang Shu <Chang.Shu at nokia.com>  2009-10-14 19:09:38 PDT ---
(In reply to comment #26)
> Note, my 1.7memory saving is not taking the QImage->QPixmap into account. In my
> benchmark asNewNativeImage is not called at all. I have created bug #30211 to
> make use of QImage instead of QPixmap for painting but I have not yet
> benchmarked it.

Can you provide some details about your test case:
1. what's the size of your image(s)?
2. Without the image, what's the memory usage?

But anyway, we can calculate the memory saving = w*h*4/2. For example, a
800x600 image saves 0.96MB.

> No. We are fixing things where they need to be fixed. I have no idea about
> constraints but you will probably have more than one patch to Qt when doing a
> release/deployment. Just add the API after Qt has agreed that it will be
> accepted.

I totally agree adding API as early as possible is great idea. This doesn't
prevent us doing the implementation at webkit level for now. Otherwise, we have
to wait for mid next year to get the job done.

> Currently I'm not really convinced that the 1.7MB is a big difference, do you
> have other data showing a bigger saving?

I won't think the memory saving will the different as long as we find out three
figures:
the "baseline": memory consumption with no image; memory consumption with image
using this 16bit conversion and without this conversion. Based on the
calculation, I feel it's worthwhile doing it on mobile platforms. Maybe a
#ifdef MOBILE is a good way to go.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.



More information about the webkit-unassigned mailing list