Re: !Cache management
In article 18f1976b54@abbeypress.net, Jim Nagel nets...@abbeypress.co.uk wrote: The runfile of my active copy in Boot Resources (which presumably came with a recent-ish version of Netsurf inside its usual boot-update file) is dated 2014-09-16, but !Sidediff shows it is identical to the 2007 runfile. This is a fact of life with several apps/systems that do auto updates each day and rebuild the download files, whatever, in that datestamps of files are updated whether they have changed or not. The ROOL hard drive image is a particular case, where it is impossible to check what, if anything has changed. -- Chris Johnson
Re: !Cache management
In article 18f1976b54@abbeypress.net, Jim Nagel nets...@abbeypress.co.uk wrote: cj wrote on 16 Nov: Is anyone else finding that the new Cache feature does not seem to expire its content? Well, that was a revelation. Did a count on !Boot.resources.!cache.caches.default.netsurf and find 222 megabytes of stuff. Earliest date seems to be Sept 06. I wondered about this having read your post. I don't have !Cache and its sub-directories but I do have !Boot.Resources.!Scrap.ScrapDirs.IDdisabled.WWW.NetSurf.Cache. In there I found I had 45 megabytes of said stuff - earliest from 2006, latest from May this year. Ah, Netsurf choices--cache. Disc cache size is set at 1024M (which I presume is meant as a max), In my case it's set at 2MB but there's no option to set the expiry. I'm using NS 3.1, 25 April 2014. I see that NS 3.2 is available on the website and the changelog mentions support for disc caching. I'll give it a go but wonder what the disk cache setting was doing in NS 3.1 if it was just storing stuff without deleting it and why the last cached item was in May this year! Alan [Snip] -- Alan Calder, Milton Keynes, UK.
Re: !Cache management
On Sun, Nov 16, 2014 at 09:49:06PM +, cj wrote: In article 20141116145722.gc21...@platypus.pepperfish.net, Rob Kendrick r...@netsurf-browser.org wrote: Currently, if NetSurf crashes (or your computer does) without quitting cleanly, newly-created cached items will be leaked; ie they will not be stored in the index which is written out on exit. Ahhh - that could explain it. My machines normally run 24/7, and the only time Netsurf is quit is when I move to the most recent version, which may be a week or more between upgrades. I do get the occasional crash of Netsurf, so it could be that a week or more of cache contents is not being indexed. This does sound like it may be the cause then. A solution (ie, detection of an unclean exit and thus a garbage collection and index rebuild etc) is on the to do list. Sadly I think the only solution at the moment however is to empty the whole cache directory manually. B.
!Cache management
Is anyone else finding that the new Cache feature does not seem to expire its content? I wondered a few weeks ago why the main harddrive on the Iyonix was filling up more quickly than I thought it should. I found the Netsurf cache was close to 10 GB in size. Netsurf was configured for a cache maximum of 1 GB with expiry set to 10 days. Randomly checking datestamps of some of the files in the cache showed them to be weeks and even months old. I had been assuming that (a) old files would be deleted after the configured expiry time and (b) if the cache size approached the configured maximum size, then the older files would be deleted anyway to keep the size under the limit. I deleted the whole cache at the time, and it is well under 1 GB at the moment, although checking a few random datestamps, there are certainly files going back to early August, even with an expiry now set to 7 days. I checked on the PandaBoard today and lo and behold, the cache contained more than 8 GB of files. This machine was also configured for a 1 GB max and 10 days expiry. I have now deleted and disabled the cache on the PandaRO. On all my machines I use recent versions of RISC OS 5.21, and recent development versions of Netsurf. Am I misunderstanding what the cache settings are? -- Chris Johnson
Re: !Cache management
On Sun, Nov 16, 2014 at 02:33:57PM +, cj wrote: I checked on the PandaBoard today and lo and behold, the cache contained more than 8 GB of files. This machine was also configured for a 1 GB max and 10 days expiry. I have now deleted and disabled the cache on the PandaRO. On all my machines I use recent versions of RISC OS 5.21, and recent development versions of Netsurf. Am I misunderstanding what the cache settings are? Currently, if NetSurf crashes (or your computer does) without quitting cleanly, newly-created cached items will be leaked; ie they will not be stored in the index which is written out on exit. We plan to have this situation detected on next start and automatically remove orphan items. At the moment, the only simple way to recover the space taken up by these lost cache items is to delete the contents of the NetSurf folder inside !Cache. B.
Re: !Cache management
In article 20141116145722.gc21...@platypus.pepperfish.net, Rob Kendrick r...@netsurf-browser.org wrote: Currently, if NetSurf crashes (or your computer does) without quitting cleanly, newly-created cached items will be leaked; ie they will not be stored in the index which is written out on exit. Ahhh - that could explain it. My machines normally run 24/7, and the only time Netsurf is quit is when I move to the most recent version, which may be a week or more between upgrades. I do get the occasional crash of Netsurf, so it could be that a week or more of cache contents is not being indexed. -- Chris Johnson
