On Ubuntu 10.04,
relatime is part of the default mount options, unless overridden in
/etc/fstab. The previous few releases had
relatime explicitly in
relatime gives the same speed (and flash write cycle conservation) benefits as
noatime, without causing trouble to old-fashioned mail notifiers.
The article you cite recommends
data=writeback. Ubuntu defaults to
data=ordered. Ubuntu's setting is slower in case of heavy disk load, but carries significantly less risk of data loss in case of a crash or power failure. So I would not recommend changing from the Ubuntu default.
commit=100 increases the time window during which data will be lost in case of a crash, for little benefit in most circumstances.
Summary: leave the settings as they are, they were chosen for a reason.
ADDED: There are other things beyond mount options than can make a difference. Switching from
ext4 is itself often a visible improvement. Here are a few more tips for laptop users.
If you have a slow SSD, check out this thread at SU. The important tips are to use
/tmp and for the browser cache (and perhaps history).
If you have a hard disk and you want it to stop spinning for extended lengths of time, then install noflushd, which allows the disk to spin down by delaying all writes until the RAM is full. (Of course, reads can cause the disk to spin up; you'll want to get into the habit of running
cat /files/I/m/likely/to/need >/dev/null before the disk spins down.) In order for noflushd to be effective, turn off all swap and mount your filesystems with something like
Using noflushd effectively means that your data can remain unwritten to disk for an extended length of time. This is a risk, to be weighed against the benefit of not having any noise or heat coming from the disk for a while. Don't use noflushd if you're not comfortable with that risk.