Woops; my mistake. For that I edited WebView::setCacheModel from this:
unsigned long long memSize = 256;
to this:
unsigned long long memSize = 32;
and I think that affects the same system, as setCacheModel calls
cache()->setCapacities() to explicitly override the default value.
That is unless I'm missing something.
Paul
i think the below is related to JS engine. i was
referring to the cached resources(css, js, images etc) -
WebCore/loader/Cache.cpp:44
static const int cDefaultCacheCapacity = 8192 * 1024;
regards,
Zaheer
On Wed, Sep 17, 2008 at 1:23 PM, Paul
Pedriana <[EMAIL PROTECTED]>
wrote:
That was discussed last
month. See the thread at:
https://lists.webkit.org/pipermail/webkit-dev/2008-August/004719.html
I am currently running my copy like this:
enum { DefaultCapacity = 2 * 256 * 1024 / sizeof(Register)};
// Originally (2 * 1024 * 1024 / sizeof(Register))
enum { DefaultMaxGlobals = 4 * 1024 };
// Originally (8 * 1024)
hi,
webkit currently reserves 8Mb of cache space (refer: Cache.cpp). This
seems too high for an embedded browser that should work with as less as
10Mb of RAM. Other than the performance/reload of resource impact are
there any side effects by reducing this or totally disabling it. one
feature that inherently relies on cache is the navigation history,
however in our tests we see that there is no impact other than the
reload (e.g. form data is preserved in navigation).
we think that a small cache ~500k is more appropriate to help for
content thats repeated in the same page being refetched.
appreciate any inputs on this.
thanks,
Zaheer
_______________________________________________
webkit-dev mailing list
[email protected]
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
|
_______________________________________________
webkit-dev mailing list
[email protected]
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
