Michael, in the case the memory leak would be in InnoDB, you can monitor its memory allocation with
SHOW INNODB STATUS\G " Total memory allocated 50738427; in additional pool allocated 1762432 " Regards, Heikki ----- Original Message ----- From: "Michael Loftis" <[EMAIL PROTECTED]> Newsgroups: mailing.database.mysql Sent: Tuesday, June 17, 2003 2:10 AM Subject: Re: MySQL 4.0.13 Memory leakage? > With editing removing any passwords or sensitive stuff. (paths is all) > > # Example mysql config file. > # You can copy this to one of: > # /usr/local/etc/my.cnf to set global options, > # mysql-data-dir/my.cnf to set server-specific options (in this > # installation this directory is /usr/local/var) or > # ~/.my.cnf to set user-specific options. > # > # One can use all long options that the program supports. > # Run the program with --help to get a list of available options > > # This will be passed to all mysql clients > [client] > port = 3306 > socket = /var/lib/mysql/mysql.sock > > # Here is entries for some specific programs > # The following values assume you have at least 32M ram > > # The MySQL server > [mysqld] > port = 3306 > socket = /var/lib/mysql/mysql.sock > datadir = /var/lib/mysql > enable-locking > > safe-show-database > > set-variable = wait_timeout=300 > set-variable = max_connections=250 > set-variable = max_user_connections=20 > set-variable = key_buffer=384M > set-variable = max_allowed_packet=4M > set-variable = table_cache=512 > set-variable = sort_buffer=2M > set-variable = record_buffer=2M > set-variable = thread_cache=8 > # Try number of CPU's*2 for thread_concurrency > set-variable = thread_concurrency=4 > set-variable = myisam_sort_buffer_size=64M > set-variable = ft_min_word_len=3 > > # Try some tuning with query caches. > set-variable = query_cache_size=64M > > # Start logging > log-bin > > server-id = 1 > > #log-slave-updates > > # Uncomment the following if you are using BDB tables > set-variable = bdb_cache_size=64M > set-variable = bdb_max_lock=100000 > > # Uncomment the following if you are using Innobase tables > innodb_data_file_path = ibdata1:128M;ibdata2:128M > innodb_data_home_dir = /var/lib/mysql/ > innodb_log_group_home_dir = /data/mysql/ > innodb_log_arch_dir = /var/lib/mysql/ > set-variable = innodb_mirrored_log_groups=1 > set-variable = innodb_log_files_in_group=3 > set-variable = innodb_log_file_size=5M > set-variable = innodb_log_buffer_size=8M > innodb_flush_log_at_trx_commit=1 > innodb_log_archive=0 > set-variable = innodb_buffer_pool_size=16M > set-variable = innodb_additional_mem_pool_size=2M > set-variable = innodb_file_io_threads=4 > set-variable = innodb_lock_wait_timeout=50 > > > [mysqldump] > quick > set-variable = max_allowed_packet=16M > > [mysql] > no-auto-rehash > > [isamchk] > set-variable = key_buffer=256M > set-variable = sort_buffer=256M > set-variable = read_buffer=2M > set-variable = write_buffer=2M > > [myisamchk] > set-variable = key_buffer=256M > set-variable = sort_buffer=256M > set-variable = read_buffer=2M > set-variable = write_buffer=2M > > [mysqlhotcopy] > interactive-timeout > > > --On Monday, June 16, 2003 16:02 -0700 Jeremy Zawodny <[EMAIL PROTECTED]> > wrote: > > > On Mon, Jun 16, 2003 at 04:41:49PM -0600, Michael Loftis wrote: > >> I'm noticing that our MySQL 4.0.13 system is probably leaking RAM > >> (uptime ~10 days) > >> > >> ... > >> PID USER PRI NI SIZE RSS SHARE STAT %CPU %MEM TIME COMMAND > >> 26046 mysql 9 0 548M 162M 44008 S 5.9 8.0 0:16 mysqld-max > >> ... > >> > >> And it just keeps growing. Even with our admittedly aggressive > >> cache settings it should have stopped a growing several days ago. > >> All processes are now at or about those memory stats. > >> > >> Any ideas? Need any more info? > > > > Without seeing your my.cnf file, it's difficult to say. > > > > Care to post it? > > -- > > Jeremy D. Zawodny | Perl, Web, MySQL, Linux Magazine, Yahoo! > > <[EMAIL PROTECTED]> | http://jeremy.zawodny.com/ > > > > MySQL 4.0.13: up 13 days, processed 440,106,660 queries (372/sec. avg) > > > > -- > > MySQL General Mailing List > > For list archives: http://lists.mysql.com/mysql > > To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] > > > > > > > > -- > Michael Loftis > Modwest Sr. Systems Administrator > Powerful, Affordable Web Hosting > > -- > MySQL General Mailing List > For list archives: http://lists.mysql.com/mysql > To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] > -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
