>>>>> "Adam" == Adam Powell <adam@stripped> writes:
Adam> Right, its Sun OS 5.6, MySQL 3.22.20a, and PHP 3.0.6. I think the problems
Adam> are caused by not adding a free statement at the end of the scripts, but I
Adam> thought PHP did a pretty good job of clearing up after itself...
On SunOS, we have run MySQL with purify to verify that there is no
memory leaks. I am also not aware of any problems with SunOS 5.6
itself. This doesn't mean that it's impossible there is a memory
leak, but only that we need more information to be able to locate it!
Have you tried to compile MySQL with --with-debug=yes ?
In this case, you can check how much memory MySQL is using by doing:
How did you verify how much memory mysqld is taking? If you have a
lot of simultaneous threads, 'ps' may calculate the thread stacks and
the space between the thread stacks in the final figure.
When mysqld starts to take a lot of memory, what values do you get
Without the above information it's very hard to say what is wrong with
your setup. Normally MySQL should take VERY little memory to resolve
a simple key lookup query !