Syndicated Linux NewsThis forum is for the discussion of Syndicated Linux News stories.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Last week, I came across a tutorial about tweaking a specific parameter in the Linux virtual memory subsystem. So I figured that I would share all of the optimizations that I usually go through in a new installation of Linux.
swappiness - it's not that important, my machine has only ever used swap when some program malfunctions and eats up all the RAM
noatime - check, knew about this one
FF cache - this is interesting, and I have never tried it, I will try it.
The one thing about swap is that, especially on low-space netbooks, it eats up precious SSD space that is even more limited than the 1GB of RAM the computer has. That's why I usually disable swap on my Acer Aspire One AOA110-1545, since it only has 8GB of space to deal with.
Yes, swap is much more important if you're using an SSD. Personally, I don't think SSDs are worth their price. It's the wrong technology for the wrong purpose.
Oh, and what exactly is the problem with putting the FF cache on /dev/shm, I've done this now because I'm lazy and I don't want extra complication. I think it'll be ok.
As the cache is exactly that, I dont forsee any problems with using it like that (and infact I guess this is why that functionality was added. However, if you follow your own guide, with the running the profile for firefox out of ram, you can see why that could cause issues;
I did NOT put the entire profile in RAM, I think that would be dangerous, just the Cache for privacy reasons more than performance reasons. I draw the line when my data is at stake.
I'm thinking of writing a container script which copies the firefox profile into a ramdrive, starts firefox from it, and then copies it back when firefox closes.
The idea seems sound, but in pratice I may find issues. Will be a nice project for me though!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.