1. Disable ipv6 and apparmor for speed up
to linux command line in /etc/default/grub then run
2. Disable wireless power saving on battery, because frankly 1 to 2 hundred milliseconds response time is too slow when you’re 20 feet from the access point.
Edit /usr/lib/pm-utils/power.d/wireless and replace any lines containing “power on” with “power off”. Not any update to pm-utils will overwrite this file and change the setting back.
3. Install Chromium as it is quite a bit faster and nicer to use than Firefox.
Remembering to keep Firefox around for the odd site that won’t work in Chromium e.g. some java based sites.
4. Add “noatime” and “commit=900” to fstab.
Gives performance increase and saves SSDs by not writing to the journal all the time.
This post isn’t designed to be a “how to” merely an overview of how I achieved the subject. It is possible to do this without any physical intervention but in practice I have had to visit site at least once to fix a boot error on every one I have done.
Disclaimer:- When attempting this having some sort of remote access solution that will give access to the server even when it won’t boot is desirable i.e. BMC, DRAC or KVM over IP. Obviously resizing and deleting partitions and file systems is very dangerous so you need to be ultra careful and ultra sure you understand the process and exactly what you are doing at each step. It may also be helpful to draw the partition layout at each stage so you have a clear view of what is happening. Don’t come crying to me when it all blows up in your face. You have been warned!
Continue reading Remotely upgrading a server from 32 to 64 bit linux