How do I use more process memory with mysqld
Mel
fbsd.questions at rachie.is-a-geek.net
Wed Apr 16 10:01:14 UTC 2008
On Wednesday 16 April 2008 10:08:44 Vikash Badal wrote:
> -----Original Message-----
>
> > From: Mel [mailto:fbsd.questions at rachie.is-a-geek.net]
> > Sent: 15 April 2008 07:52 PM
> > To: freebsd-questions at freebsd.org
> > Cc: Vikash Badal
> > Subject: Re: How do I use more process memory with mysqld
> >
> > On Tuesday 15 April 2008 17:07:14 Vikash Badal wrote:
> > > datasize 33554432 kB
> >
> > That says 3G.
> >
> > > 48647 mysql 35 20 0 963M 938M kserel 0 718.9H
> >
> > 22.17% mysqld
> >
> > Your my.cnf is missing. Are you sure you're allowing mysql to
> > go beyong 1G?
>
> Sorry about that ... Missed that one.
>
> My.cnf:
> ~~~~~~~~~~
> # The MySQL server
> [mysqld]
> key_buffer = 768M
> max_allowed_packet = 2M
> table_cache = 1024
> sort_buffer_size = 4M
> read_buffer_size = 4M
> read_rnd_buffer_size = 16M
> myisam_sort_buffer_size = 128M
> thread_cache_size = 8
> query_cache_size = 64M
> max_connections = 200
key_buffer_size + (read_buffer_size + sort_buffer_size) * max_connections =
max_mem_usage:
768 + (4 + 4) * 200 = 2368
From the 963 shown in top, I'm guessing you're around 22 concurrent
connections. The key buffer is allocated on start up, read/sort buffer on per
connection base. So if you want it to use more memory, put more in the key
buffer and make sure to leave 1.6G for your max connections.
--
Mel
Problem with today's modular software: they start with the modules
and never get to the software part.
More information about the freebsd-questions
mailing list