I wish to configure Chromium to minimise writes to Flash memory. The cache is the big one, and I ended up killing it this way:
# ln -s /dev/null /root/.cache
Chromium does complain at startup, but this method does work.
I wanted to know what commandline options there are, but the 'man' page has hardly anything. Instead, you have to look in the source code:
Apparently, these switches are not stable and liable to change at the whim of the developers.
One guy made ~/.config/chromium/Default/History and ~/.config/chromium/Default/Thumbnails into symlinks to /dev/null, as this files get written to a lot.
However, this causes an error message popup window at startup, although the browser still works. I was not able to suppress that error window.
Comments:Posted on 8 Jul 2012, 8:06 by technosaurus
I guess you could symlink to /dev/null but isn't puppy's /tmp and /dev/shm both tmpfs. Wouldn't that make more sense... Unless you have one of those mythical _true_ unlimited data plans and load speed are not an issue
Posted on 8 Jul 2012, 8:57 by BarryK
But such tiny ram
The worry I have with using a tmpfs is that ram is only 256MB on the RP. Putting more and more stuff into the tmpfs while surfing with Chromium will reduce the available ram, and gradually choke the whole system.
There is a commandline option to limit cache size, but it doesn't work. Perhaps that is because we have an older version of Chromium in Debian Squeeze.
Posted on 10 Jul 2012, 15:06 by disciple
have you checked out browsers designed for running from flash in a low memory environment?
There are/were a number of projects (e.g. gpe, matchbox) to essentially produce loosely coupled "desktop environments" for mobile devices. On some of them the apps don't really look different from typical desktop apps. But their design should target "a low memory and flash footprint".
Have you looked at whether any of them have a suitable browser for Puppy?
Which reminds me... I need to check out gpe-filemanager some time.
Posted on 12 Jul 2012, 10:38 by PeterM321
--disk-cache-size=xxx (in bytes)
You can check the Current Cache size & Max size by heading over to chrome://net-internals/#httpCache page
But also there is the possibility to create a small ramdisk:
mount -t tmpfs -o size=5m /dev/shm /tmp/ccache
ln -s /tmp/ccache/.cache /root/.cache
And see if Chromium can tolerate the small limit.