Hi,
I am using DB2 v9.5 FP2a on two different Linux distro Suse Linux 10 sp1 (IBM mainframe System z) and Ubuntu 8.10 (Intel Sytem x server).

I have been reading some articles that suggest to set Linux kernel parameter noatime in /etc/fstab to increase read performance. Linux kernel by default makes writes! to disk for every file it reads! just to update last access timestamp of file it was accessed. This produces way to many disk IO operations totally unnecessary.

There is article from IBM web page Tuning LAMP systems, Part 1: Understanding the LAMP architecture: "The first order of business is to ensure that atime logging is disabled on file systems. The atime is the last access time of a file, and each time a file is accessed, the underlying file system must record this timestamp. Because atime is rarely used by systems administrators, disabling it frees up some disk time. This is accomplished by adding the noatime option in the fourth column of /etc/fstab."

More info on this topic:
Reducing Disk IO By Mounting Partitions With noatime for Ubuntu
The atime and noatime attribute
Optimizing filesystem access
Linux kernel developers

I have checked on my Ubuntu 8.10 system and there is:
I have checked on Suse Linux 10 sp1 and there is /db2 disk partition with the following options:
According to article there sould be set for Ubuntu:
and for Suse:
I can't find any articles that recommends this settings for DB2. But if there is recommendation for MySQL it is probably as well suitable for DB2.

Questions:
1. How is this this noatime parameter set on your DB2 database Linux environment? Can you please check yours /etc/fstab file?
2. Has anybody measured performance benefits using SQLs (especialy select statemsts) using this kernel settings?

Regards,
Grofaty