David E. Ross wrote:
On 8/9/2016 10:37 PM, Paul B. Gallagher wrote:
David E. Ross wrote:
However, what I see is that the same Web page -- my own on a Web
server -- loads much slower if it is the first Web page I request
right after launching SeaMonkey. If I clear my cache and then
request it again, it load very quickly.
That would make sense if SeaMonkey's routine that checks the cache
before retrieving a remote copy is inefficient. Then the fuller the
cache, the more hunting it has to do before giving up, whereas it can
quickly evaluate an empty cache as lacking the desired content.
I always purge my cache on termination. At [Edit > Preferences >
Privacy & Security > Private Data], I have checkmarks in the check boxes
for "Always clear my private data when I close SeaMonkey" and (under
"When I ask SeaMonkey to clear my private data, it should erase")
"Cache" and "Offline Website Data". Thus, my cache should be empty on
launching SeaMonkey.
So do I, which makes your scenario peculiar.
If SM launches with an empty cache (assuming a normal shutdown of the
previous session), how does clearing cache later create a different
environment that allows the page to load quickly? How is an empty cache
different from an empty cache? Or are you clearing something else that
does make a difference? For example, I've sometimes noted differences in
performance after I clear cookies.
--
War doesn't determine who's right, just who's left.
--
Paul B. Gallagher
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
