View Single Post
  #3 (permalink)  
Old 01-02-09, 04:25
grofaty grofaty is offline
Registered User
 
Join Date: Jan 2003
Posts: 1,563
Quote:
Originally Posted by JAYANTA_DATTA
In some cases it works great and in some other cases, it shows no improvement.
What gain attention to me was two things: (a) On IBM page was suggestion to set this setting for MySQL database and (b) is the sentence from Linux kernel developers debate: "Whenever you read from a file, even one in memory cache.... do a write!" So if I understand correctly even if data in database are in bufferpool every time that data are accessed from memory an update of timestamp for atime is given. If I understand correctly this could have an impact. And then few posts later: "I didnt mean to say that it is _always_ a big issue, but "only a small number of files are read" is a very, very small minority of even the database server world."

Quote:
Originally Posted by JAYANTA_DATTA
This is from one of those different article "This option works the best if external storage is used, for example, SAN."
You probably read this from Linux Tuning Parameters web site. And yes, we are using external storage, Linux on "System z" we are using Enterprise Storage Server.

Quote:
Originally Posted by JAYANTA_DATTA
In our system (Linux 2 version6 with 64 GB and 8 CPU), this is not being used but having no issues with I/O.
We also don't have a IO performance problem. But what I am wondering is: "Do we have no disk IO problems because we have a 'big machine' and if we can lower down disk IO, could we have a smaller machine?"

Last edited by grofaty; 01-02-09 at 04:32.
Reply With Quote