In article <[EMAIL PROTECTED]>, Jeremy Zawodny <[EMAIL PROTECTED]> writes:
>> > Using the query cache at all? >> >> Not sure... I'm using the values for caches and whatnot from the >> my-large.cnf in the distribution. > The my-large.cnf I'm looking at has a 16M query cache, but doesn't > explicitly turn it on. See what "show variables like 'query_ca%" says: mysql> show variables like 'query_ca%'; > +-------------------+----------+ > | Variable_name | Value | > +-------------------+----------+ > | query_cache_limit | 1048576 | > | query_cache_size | 33554432 | > | query_cache_type | DEMAND | > +-------------------+----------+ > 3 rows in set (0.01 sec) > You see "demand" there because we set query_cache_type = 2. But if > you had "= 1" you should see either "ON" or "ENABLED", I don't > remember which. If not, it's probably OFF or DISABLED. The query cache might help somewhat when looking up users/passwords, but it won't help at all with the relay table because it changes too often. Moreover, if your analysis is correct, Charles does not have a MySQL problem at all, so I wouldn't bother to mess with it. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
