Hello.
As I said in my last mail, you can tell MySQL how much memory to use.
On Fri, Mar 30, 2001 at 03:44:14PM +0100, [EMAIL PROTECTED] wrote:
> At 18:52 29/03/01 +0200, you wrote:
>
> Hello again!
>
> >Sorry but didn't see your other comments on first reading.
>
> I thought that the key cache meant that mysqld would only hold
> key/indexes in memory and that the data the indexs point to would
> still be read/written from disk.
Yes.
> It's just that it seems to me that mysqld allocates memory for the
> indexes and the data they point to, to enable the data set to be
> retrieved.
Correct.
> And that when an additional table is
> used by a client, the server's memory manager allocates additional memory
> to cope with new query rather than using the memory that it has already
> grabbed.
Correct. As long as it hasn't reached the specified limit.
> I can't belive that it should work this way because mysqld would would
> allways eat up memory to the sum of all the data of all the tables used.
It wouldn't because there is a limit, which you should to a reasonable
value.
> The only way I have found of forcing mysqld to deallocate memory is
> to drop one of the tables previously used in a select statement -
> not much use! I have read 90% of MySQL by Paul DuBois and can't
> find an answer!? Any ideas? cheers
Have a look at the output of "mysqladmin variables", especially
key_buffer_size (I think it's named so).
> Shaun.
>
> i'm using:-
> mysql version 3.23.33
> Linux Box - kernel 2.4 (swap disabled)
>
[...]
> >
> >Yes. MySQL has a key cache (and some other caches) which are used to
> >optimize speed. You can specify the size of the caches on start-up.
> >
Bye,
Benjamin.
---------------------------------------------------------------------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
