X-Git-Url: http://git.iain.cx/?a=blobdiff_plain;f=BUGS;h=7194db2208faa2fbfcb9ce5d54711312faa39da3;hb=6e1a36f58c73ec770b55701bd8ae26d06ef4f8a5;hp=2556f67c0db992f9b2657fe50b5874003e3daed3;hpb=bba62c7e1fa806db54a4bb0e898b1cc5e952b2c8;p=pstop.git

diff --git a/BUGS b/BUGS
index 2556f67..7194db2 100644
--- a/BUGS
+++ b/BUGS
@@ -1,19 +1,29 @@
 Bugs
 ----
 
-See also NEW_FEATURES for things which probably need adding soon. 
+See also NEW_FEATURES for things which probably need adding soon.
 
 1. Show the binlogs completely and match them properly
 by looking at the pattern defined in the server. Currently I'm using
 hard-coded stuff which matches personal usage.
 
-2. Only tested on MySQL 5.6 and MariaDB 10.0. It should be possible
-to make this work on MySQL 5.7 but that has not been tested yet.
-
-3. Latency issues over slow connections. Perhaps should use compressed
+2. Latency issues over slow connections. Perhaps should use compressed
 connection to speed things up?
 
-4. Inefficient collection of data. I'm calculating stuff for the
-things I'm not actually displaying, so I should split this so that
-the display part does the calculations when needed and only the raw
-values are collected.
+3. Sometimes I see this:
+
+pstop 0.0.12 -  8:46:41 xxxxxxxxxxxxx / 5.6.21-log, up 1d 22h 59m 16s   [ABS]
+Latency by Table Name (table_io_waits_summary_by_table) 239 rows
+Table Name                        Latency      %| Fetch Insert Update Delete
+xxx.xxxxxxxx                    5124.10 h +++.+%|100.0%
+xxxxxx.xxxxxxxxxxxx             5124.10 h +++.+%|100.0%
+xxxxxx.xxxxxxx                  5124.10 h +++.+%|100.0%
+xxxxxxxx.xxxxxxxxxx             5124.09 h +++.+%|100.0%
+xxxxxxxx.xxxxxxxx               5124.09 h +++.+%|100.0%
+xxxxxx.xxxx                      00:07:49  49.2%| 98.6%   0.3%          1.1%
+xxxxxxxxx.xxxxxxxxxxx            00:06:23  40.2%| 97.4%   2.4%          0.1%
+xxxxxxxxx.xxxxxxxxxx              26.25 s   2.8%|114.2%   0.1% +++.+%   0.0%
+xxxxxx.xxxxxxxx                   15.71 s   1.6%| 99.6%   0.4%
+
+with a very long latency. Related to doing backups. Need to check the cause
+of the 5124.10h ++ issue. Probably a subtraction problem of some sort.