Hello Members, so far my USB external 'solid-state' drive, with the Cruchbang 10 Xfce OS installed runs very well on my Macbook's, but I'm always looking to see if improvements can be made, especially with regards to browser speed.
I've been using Google Chrome rather than Chromium for a few weeks now, and prefer it, so while browsing the web i came across a few articles regarding Chrome's cache, namely changing where it is kept, or how it's used to make it run even faster, link below
Have members tried these instructions in Crunchbang, especially if they've the same set-up as me. The link describes the process when running Ubuntu, so i wouldn't know if it's possible to do this Crunchbang.
Also, are there sacrifices regarding the preserving of any browser history, or data when caching in RAM? and when doing this using a Macbook should anything else be considered?
It's a question if /var/tmp or /tmp/ram/ are in RAM.
This solution looks more sexy: https://bbs.archlinux.org/viewtopic.php … 85#p967385 - no warranty, I haven't tested it (yet, but I can do it later when I'm back on netbook)
seems better to me.
Ha ezt el tudod olvasni, biztosan nem vagy rövidlátó.
Thanks machinebacon, Istvan, sorry for slow reply, i'm guessing Istvan's way is going to be easier for me and that as each method points Chrome to using just the RAM for it's cache, nothing get remembered when browsing.
machinebacon, did you try it out, and was there any noticeable benefit?
Well, pointing the cache directory to /tmp or /var/tmp will only work, as machinebacon said, if one of those folders is a tmpfs already. Let's have a look at your /etc/fstab and the output of mount, shall we?
The most sane and clean approach would be creating a folder (e.g. user_cache) in /tmp that is mounted as tmpfs, and chreate a hierarchy per user:
user[0-9] would be the names of the users, of course. Those folders and the child folders would need to be mode 700 (or 730 or 733, if you want other users to read your cache - not recommended). Then all you need is symlinks from the home folders of those users to the respective cache folders.
- You will only have to deal with one entry in the fstab
- Your fstab does not point to a single user's home folder (which is ugly)
- Users can activate and deactive RAM tmp without root access or a slow fuse setup.
- 5mins work
- nothing really.
I'm so meta, even this acronym
Just an update, i gave IstVan's method a go and typed the instructions he posted into a terminal window, both command versions opened Chromium rather than the Chrome browser, if i changed the word 'chromium' in these commands to 'chrome' this didn't work, so i guess Chrome's files are in another location.
What i did notice, is that the command below.....
....seemed to feel faster between the two suggested, but i really couldn't see a great difference between running Chromium using these commands (cacheing in RAM), or running Chromium from its normal desktop menu launcher,
I not to sure how i 'tmpfs' the /tmp (temp folder), or whether there's any real speed gain in doing this?
I think I'll see what results machinebacon comes to before struggling to work out all the details to make the necessary changes.
Why is an fstab pointing to a single user's folder bad if you only ever log in as that user? I have my ~/tmp mounted in RAM and haven't had any issues.
An easy method of adding command-line parameters to every instance of chromium-browser is to set an environment variable in ~/.profile :
export CHROMIUM_USER_FLAGS="--disk-cache-dir=/tmp --disk-cache-size=52428800"
After your next login, these parameters will get applied no matter how you launch chromium. I've got a tmpfs mounted on /tmp, so this puts my cache in RAM and limits the size to 50MB.