Even with only 16 Mo, your query cache is quite efficient (78% of your
queries are fetched directly from the cache).
Try to increaze your query_cache_size until there's no more additional
lowmem_prunes reported.
And executed from time to time FLUSH QUERY CACHE to defragment your
query cache.
Thanks these are fresh results
| query_cache_limit| 1048576 |
| query_cache_min_res_unit | 4096 |
show status like "ques%";
+---+--+
| Variable_name | Value|
+---+--+
| Questions | 14189604 |
+---+--+
sho
In the last episode (Mar 09), Mauricio Pellegrini said:
> Thanks, this the result of show status like "qcache%"
>
> +-+--+
> | Variable_name | Value|
> +-+--+
> | Qcache_free_blocks | 3330 |
> | Qcache_free_mem
Hi,
How many questions for thoses results ?
There's a lot of lowmem_prunes, so I would indeed increase the memory
size to reduce the risk of lowmem_prunes.
What is your query_cache_limit ?
Jocelyn
Mauricio Pellegrini a écrit :
Thanks, this the result of show status like "qcache%"
+
Thanks, this the result of show status like "qcache%"
+-+--+
| Variable_name | Value|
+-+--+
| Qcache_free_blocks | 3330 |
| Qcache_free_memory | 13372320 |
| Qcache_hits | 9149 |
| Qcache_
In the last episode (Mar 09), Mauricio Pellegrini said:
> Hi, I'm trying to tweak the execution time for querys on my mysql
> server which is using InnoDB.
>
> I know that there are a lot of things to check but one of them,
> perhaps not the most important, is the query_cache_size.
>
> I have a d
Depends on the result sets you want to cache. Check the other variables in the
manual, you can analyze if all the query cache is utilized at a point in time.
In general 16M is low when you have 4GB, you can safely increase it.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PRO
