Re: Reduce the server load by asking firefox to not cache on disk
On Wed, May 15, 2013 at 06:05:52PM +0200, Alf Tonny Bätz wrote:
> i have taken a look on that packages, its copy real iceweasel til
> iceweasel_real so when user click iceweasel the script copy the .mozilla
> folder to tmp, and call icewasel_real after its done. And when user exit
> iceweasel the script copy the .mozilla from tmp back to users home
> folder..
>
> I like this approach
Our teachers and Skolelinux support teams liked it, too, since it is
non-intrusive to iceweasels normal way of operation, iceweasel just uses
a different directory (which is on the ramdisk in our scenario) for
frequent writes.
There are two disadvantages, though:
1. In case the user configures a HUGE disk cache, lots of data are
copied forward and back, so a problem may occur when many users quit
their firefox at once (i.e. at the end of the lesson). Solution: Combine
with the "small/no disk cache" approach.
2. In case the user logs out or kills his/her session without quitting
firefox, changes to bookmarks from this session are lost. Well... This
may happen without the script, too (kill -9).
The script should detect stale symlinks, and remove them automatically
in case there is a leftover $HOME/.mozilla from the previous session.
Regards
-Klaus
Reply to: