maria-developers team mailing list archive

[worklog-noreply@xxxxxxxxxxxx]

-----------------------------------------------------------------------
                              WORKLOG TASK
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
TASK...........: Provide key cache statistics
CREATION DATE..: Thu, 22 Oct 2009, 12:28
SUPERVISOR.....: Bothorsen
IMPLEMENTOR....: 
COPIES TO......: 
CATEGORY.......: Server-RawIdeaBin
TASK ID........: 58 (http://askmonty.org/worklog/?tid=58)
VERSION........: WorkLog-3.4
STATUS.........: Cancelled
PRIORITY.......: 60
WORKED HOURS...: 0
ESTIMATE.......: 0 (hours remain)
ORIG. ESTIMATE.: 0

PROGRESS NOTES:

-=-=(Guest - Thu, 14 Jan 2010, 15:15)=-=-
Status updated.
--- /tmp/wklog.58.old.19489     2010-01-14 13:15:35.000000000 +0000
+++ /tmp/wklog.58.new.19489     2010-01-14 13:15:35.000000000 +0000
@@ -1 +1 @@
-Un-Assigned
+Cancelled

-=-=(Monty - Fri, 27 Nov 2009, 12:36)=-=-
High Level Description modified.
--- /tmp/wklog.58.old.15108     2009-11-27 10:36:13.000000000 +0000
+++ /tmp/wklog.58.new.15108     2009-11-27 10:36:13.000000000 +0000
@@ -1,8 +1,7 @@
-Provide the key cache  
-statistics available for the default cache (key blocks used,  
-unflushed, etc.) for all named caches.
+Provide the same key cache statistics for all MyISAM key caches as we provide
+for the default key cache.
 
-Monty answers in an email:
+Background: Monty answers in an email to customer:
 
 This is a much simpler task and something that is important to get
 done.  We would have to introduce a 'show keycache statistics' command
@@ -11,3 +10,44 @@
 The raw coding is probably 1-2 days, but on top if this we need
 testing, a test environment and building of biniaries for you.
 Henrik/Bo and Igor will come back to you with a more exact estimate.
+
+-----------------
+Currently we have:
+
+show status like "key%";
++------------------------+-------+
+| Variable_name          | Value |
++------------------------+-------+
+| Key_blocks_not_flushed | 0     |
+| Key_blocks_unused      | 13389 |
+| Key_blocks_used        | 7     |
+| Key_read_requests      | 22    |
+| Key_reads              | 7     |
+| Key_write_requests     | 0     |
+| Key_writes             | 0     |
++------------------------+-------+
+
+Sergei suggested we introduce for each new key cache a set of variables prefixed
+with the keycache name:
+
+show status like "keycache1.%";
+Which should show:
+
++----------------------------------+-------+
+| Variable_name                    | Value |
++----------------------------------+-------+
+| keycache1.Key_blocks_not_flushed | 0     |
+| keycache1.Key_blocks_unused      | 13389 |
+| keycache1.Key_blocks_used        | 7     |
+| keycache1.Key_read_requests      | 22    |
+| keycache1.Key_reads              | 7     |
+| keycache1.Key_write_requests     | 0     |
+| keycache1.Key_writes             | 0     |
++----------------------------------+-------+
+
+The task would thus to be to automatically introduce new variables when we
+create a new key cache and automatically remove these variables when the cache
+is deleted.
+
+The other option would be to add an information schema where we populate the
+information schema with data from all existing key caches.



DESCRIPTION:

Provide the same key cache statistics for all MyISAM key caches as we provide
for the default key cache.

Background: Monty answers in an email to customer:

This is a much simpler task and something that is important to get
done.  We would have to introduce a 'show keycache statistics' command
that would iterate over all keycaches and provide the statistics.

The raw coding is probably 1-2 days, but on top if this we need
testing, a test environment and building of biniaries for you.
Henrik/Bo and Igor will come back to you with a more exact estimate.

-----------------
Currently we have:

show status like "key%";
+------------------------+-------+
| Variable_name          | Value |
+------------------------+-------+
| Key_blocks_not_flushed | 0     |
| Key_blocks_unused      | 13389 |
| Key_blocks_used        | 7     |
| Key_read_requests      | 22    |
| Key_reads              | 7     |
| Key_write_requests     | 0     |
| Key_writes             | 0     |
+------------------------+-------+

Sergei suggested we introduce for each new key cache a set of variables prefixed
with the keycache name:

show status like "keycache1.%";
Which should show:

+----------------------------------+-------+
| Variable_name                    | Value |
+----------------------------------+-------+
| keycache1.Key_blocks_not_flushed | 0     |
| keycache1.Key_blocks_unused      | 13389 |
| keycache1.Key_blocks_used        | 7     |
| keycache1.Key_read_requests      | 22    |
| keycache1.Key_reads              | 7     |
| keycache1.Key_write_requests     | 0     |
| keycache1.Key_writes             | 0     |
+----------------------------------+-------+

The task would thus to be to automatically introduce new variables when we
create a new key cache and automatically remove these variables when the cache
is deleted.

The other option would be to add an information schema where we populate the
information schema with data from all existing key caches.


ESTIMATED WORK TIME

ESTIMATED COMPLETION DATE
-----------------------------------------------------------------------
WorkLog (v3.5.9)