Acrobat (Netscape cache settings)

[Earl Young]

     A cache that is too large generates problems because it will collect 
     many hundreds of files and build a long index that has to be queried 
     each time you hit a page.  I ran into similar problems with a cache 
     size of 10 MB on sites where I was running into lots of small files.  
     The small files model is a typical Web event.  I too came back to the 
     5MB cache.
     
     One way to tell that your cache is too small is that you run into 
     reload situations during the "back" process.  One of the reasons that 
     "back" typically loads a page faster than was the case when you first 
     hit the page is that "back" hits the cache and not the net.  If the 
     cache is too small as you use it, your "back" commands will hit the 
     Web instead.
     
     Pages with monster graphics step on the cache harder than pages with 
     smaller files, thus your use of the Web also is a factor in cache 
     size.
     
     Earl Young


______________________________ Reply Separator _________________________________
Subject: Re: Acrobat (Netscape cache settings)
Author:  moseley at netcom.com at INTERNET
Date:    2/4/97 10:54 AM


One thing to note about Netscape's cache settings -- I had the disk cache 
on Netscape 3.0 32 bit set large -- can't remember exactly, but I think 
20MB.  I don't remember the exact problem, but Netscape did fail to work 
properly with this setting.
     
With the cache set so large, it took a while for this problem surface 
(which was the clue that it was a cache problem).  Setting it back to 5MB 
fixed the problem.
     
It would be very interesting to see what percent of the web pages accessed 
are in the cache.
     
     
     
     
Bill Moseley
mailto:moseley at netcom.com