Bug #27323 | Query cache | ||
---|---|---|---|
Submitted: | 21 Mar 2007 10:54 | Modified: | 23 Apr 2007 13:07 |
Reporter: | Tordjman Yohan | Email Updates: | |
Status: | No Feedback | Impact on me: | |
Category: | MySQL Server | Severity: | S2 (Serious) |
Version: | 5.0.32 / 5.0.37 | OS: | Linux (linux) |
Assigned to: | CPU Architecture: | Any | |
Tags: | cache, query |
[21 Mar 2007 10:54]
Tordjman Yohan
[23 Mar 2007 10:49]
Sveta Smirnova
Thank you for the report. From which version did you update? Please also provide queries you think should be cached.
[23 Mar 2007 11:01]
Tordjman Yohan
i have upgraded from an old debian sid version to the last debian sid version (5.0.32). the queries are very simple: select login from passwd where password = 'xxxx'; => the server take 90% cpu in ~1h of work. It do ~600 resquet/s i compiled/installed mysql 5.0.37 myself and same thing. i tuned some parameters(1) and now it seems good for the cpu... but i really don't understand that: | Questions | 89934873 | | Qcache_free_blocks | 41567 | *| Qcache_free_memory | 137077432 |* | Qcache_hits | 45458858 | | Qcache_inserts | 44315836 | *| Qcache_lowmem_prunes | 40438036 |* | Qcache_not_cached | 2870 | | Qcache_queries_in_cache | 128270 | | Qcache_total_blocks | 298108 | how can be Qcache lowmem_prunes and 130Mo of Qcache free memory ? (1) key_buffer = 384M thread_stack = 256K query_cache_limit = 65536 query_cache_size = 256M query_cache_type = 1
[23 Mar 2007 11:45]
Sveta Smirnova
Please read why Qcache_lowmem_prunes increases starting at http://dev.mysql.com/doc/refman/5.0/en/query-cache-configuration.html Also note we need repeatable test case from you showing why you consider it is our bug.
[23 Mar 2007 12:19]
Tordjman Yohan
Ok so i'm trying with smaller query_cache_min_res_unit and do a report if i see some problems... thanks
[23 Mar 2007 13:07]
Sveta Smirnova
Thank you. Will wait feedback from you.
[23 Apr 2007 23:00]
Bugs System
No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open".