[webkit-dev] JS binding wapper pointers: inline vs. separate hash table
mjs at apple.com
Thu Oct 2 11:19:44 PDT 2008
On Oct 2, 2008, at 11:14 AM, Mike Hommey wrote:
> On Thu, Oct 02, 2008 at 11:06:19AM -0700, Maciej Stachowiak wrote:
>> On Oct 1, 2008, at 10:41 PM, Mike Hommey wrote:
>>> On Wed, Oct 01, 2008 at 04:03:32PM -0700, Mike Belshe wrote:
>>>> Total size Potential savings
>>>> www.cnn.com: 43M
>>>> 43M 408K
>>>> www.slashdot.org: 36M 208K
>>>> m.ext.google.com: 45M 475K
>>>> docs (normal doc): 42M 341K
>>>> docs (big spreadsheet): 55M 905K
>>>> maps: 38M 159K
>>> It would be interesting to have the figures on 64-bit systems.
>> The extra space is all pointers so the size cost would double.
> Sure, but what would be interesting is the comparison with the total
> size, which isn't 100% pointers.
Yes, the total cost would likely less than double. The DOM is mostly
pointers, the render tree is maybe half pointers, and image data would
not change size at all. So proportionately, it would be more expensive
More information about the webkit-dev