> > I have a 3.23.56 installation compiled with:
> >
> > ./configure --with-innodb --prefix=/usr/local/mysql
> > --with-mysqld-user=mysql
> >
> > Freebsd 4.6.2, dual processor with 512M Ram.
>
> [snip]
>
> > When mysqld is initially started, resident memory as shown by top is
> > 317M. This figures climbs steadily by about 60M per day, until it
> > reaches 512M approx. at which point mysqld stops
> responding, consumes
> > all available CPU and logs Out of memory (Needed X bytes)
> to it's error
> > log. Running truss on the mysqld process at that point
> shows repeating:
> > break(0x282a2000) ERR#12 'Cannot allocate memory'
> >
> > I attribute this behaviour to mysqld having reached FreeBSD's per
> > process memory limit of 512M, however my theory about this could be
> > wrong.
> >
> > Assuming this is the case, I could recompile the FreeBSD
> kernel to raise
> > this limit, however I do not really want to do that as our
> kernel config
> > is standard site wide and the box has only 512M total
> memory anyway. I
> > would rather understand why mysqld's memory usage is
> climbing seemingly
> > indefinitely and prevent it from doing so.
> >
> > I understand that the two 1M buffers in the my.cnf above
> can be assigned
> > on a per connection basis, so the total memory usage could
> theoretically
> > exceed 512M, but I don't think this is the issue as I have
> had a 3.23.39
> > installation compiled without InnoDB running on the same
> box for many
> > months with the same set of clients. All that has changed
> is the version
> > and the InnoDB being included. The memory consumption
> climbs gradually,
> > suggesting that memory is being assigned and not released.
>
> Are you using InnoDB at all?
Yes, I am using InnoDB. All but one table in the one database (apart
from the mySQL system database) on the server is InnoDB, total size of
all tables is approximately 250M. 75 - 100 queries per second, mostly
selects.
