[Webkit-unassigned] [Bug 33178] New: Segmented SharedBuffer: SharedBuffer doesn't have to be a flat memory block

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Mon Jan 4 12:49:22 PST 2010


           Summary: Segmented SharedBuffer: SharedBuffer doesn't have to
                    be a flat memory block
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: WebCore Misc.
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: yong.li.webkit at gmail.com
                CC: staikos at kde.org

Currently, SharedBuffer uses Vector<char> as the internal buffer, and stores
all resource data in the flat vector. When more resource data comes and the
buffer size is not big enough, SharedBuffer will allocate a new buffer, and
copy all bytes to the new buffer.

The purpose of this bug report is to allow SharedBuffer to use a group of
memory segments to store resource data, and also enable image/text decoders to
decode from segmented source data. This will reduce peak memory usage and also
avoid requests for huge memory blocks. For desktop browsers, it is probably not
that helpful, but from my testing, it seems not hurting the performance. I
tested segmented SharedBuffer with modified text decoders, jpeg decoder and png
decoder against iBench using Safari win32, and the result is segmented
SharedBuffer is roughly 1% faster.

Patches are coming.

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