Bugzilla

I just noticed something rather interesting, testing with the same three noisy pages on Firefox and Chrome: The average "resident data size" of an IOAccelResource object (as returned by IOAccelResourceGetResidentDataSize()) is much smaller on Chrome than on Firefox. So is the total size of all IOAccelResource objects created during standardized tests of these three pages, though the number of IOAccelResource objects created by Chrome is twice that created by Firefox. I didn't count objects with zero "resident data size".

As best I can tell, a resource's "resident data size" is the amount of wired video memory it takes up when paged in, and the amount of wired system memory it uses for backing store while it can still be paged in or out.

This doesn't apply to Safari, whose average "resident data size" is about the same as Firefox's, and whose total "resident data size" is about twice as large. But then Safari seems to have its own (Metal based) strategy for "purging" resources, used by neither Chrome or Firefox.

I'll see what I can make of this. It's my first real lead in quite a long time.

I just noticed something rather interesting, testing with the same three noisy pages on Firefox and Chrome: The average "resident data size" of an IOAccelResource object (as returned by IOAccelResourceGetResidentDataSize()) is much smaller on Chrome than on Firefox. So is the total size of all IOAccelResource objects created during standardized tests of these three pages, though the number of IOAccelResource objects created by Chrome is twice that created by Firefox. I didn't count objects with zero "resident data size".

As best I can tell, a resource's "resident data size" is the amount of wired video memory it takes up when paged in, and the amount of wired system memory it uses for backing store while it can still be paged in or out.

This doesn't apply to Safari, whose average "resident data size" is about the same as Firefox's, and whose total "resident data size" is about twice as large. But then Safari seems to have its own (Metal based) strategy for "purging" resources, used by neither Chrome nor Firefox.

I'll see what I can make of this. It's my first real lead in quite a long time.