On Wed, Feb 16, 2005 at 04:18:41AM +0900, SODA Noriyuki wrote:
> > (of course, what databases that do their own caching really want is
> > unbuffered I/O, but mysql appears to rely on the OS file cache since
> > the mysqld process is only 60MB on this machine with 3GB of RAM.
> > maybe that's just how it's configured by default,
> 
> The MySQL configuration that the author of the report used is
> described in previous article:
> http://software.newsforge.com/software/04/12/27/1238216.shtml?tid=72&tid=29
> 
> i.e.
> innodb_buffer_pool_size=256M
> innodb_log_file_size=128M
> innodb_log_buffer_size=8M
> innodb_flush_log_at_trx_commit=1
> 
> Since the machine only has 512MB RAM, more than half of the memory
> (256MB+8MB) are allocated to the database cache.

hmm, I had applied those setting without paying attention to what they were.
even with those, the mysqld process never got above 60-odd MB in size.
it's not using any sysv shared memory, so where is the cached data going?
I'm sure I'm just being dense here.  :-)

-Chuck