← Back to team overview

percona-discussion team mailing list archive

Updated Invitation: patch for more InnoDB disk IO status... @ 2009-08-26 08:00 – 08:15 (percona-discussion@xxxxxxxxxxxxxxxxxxx)

 

BEGIN:VCALENDAR
PRODID:-//Google Inc//Google Calendar 70.9054//EN
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:REQUEST
BEGIN:VEVENT
DTSTART:20090826T050000Z
DTEND:20090826T051500Z
DTSTAMP:20090824T112418Z
ORGANIZER;CN=Aleksandr Kuzminsky:mailto:aleksandr.kuzminsky@xxxxxxxxxxx
UID:85iae84ube1br04qn3k3nke4g0@xxxxxxxxxx
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=percona-discussion@xxxxxxxxxxxxxxxxxxx;X-NUM-GUESTS=0:mailto:percon
 a-discussion@xxxxxxxxxxxxxxxxxxx
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=mdcallag@xxxxxxxxx;X-NUM-GUESTS=0:mailto:mdcallag@xxxxxxxxx
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=Aleksandr Kuzminsky;X-NUM-GUESTS=0:mailto:aleksandr.kuzminsky@perco
 na.com
CLASS:PRIVATE
CREATED:20090824T112337Z
DESCRIPTION:Thanks Mark\,\n\nI am going to include it into releases.\n\nAle
 xandr\, can you prepare patch for our LP tree ?\n\n\nOn Thu\, Aug 13\, 2009
  at 12:24 AM\, MARK CALLAGHAN<mdcallag@xxxxxxxxx> wrote:\n> I have attached
  a patch that adds more InnoDB disk IO status in SHOW\n> INNODB STATUS for 
 5.0.84 percona high perf build 18. The patch is BSD\n> courtesy of Facebook
 . Among other things\, this will display whether\n> requests are balanced a
 cross the background IO threads. And if you\n> don't want it in a productio
 n release\, it is still useful for\n> verifying performance tests.\n>\n> Ou
 tput looks like this:\n>\n> --------\n> FILE I/O\n> --------\n> I/O thread 
 0 state: waiting for i/o request (insert buffer thread) 0\n> requests\, 0.0
 0 bytes/r\, svc: 0.00 secs\, 0.00 msecs/r\, 0.00 max msecs\n> I/O thread 1 
 state: waiting for i/o request (log thread) 111 requests\,\n> 16384.00 byte
 s/r\, svc: 0.00 secs\, 0.01 msecs/r\, 0.03 max msecs\n> I/O thread 2 state:
  waiting for i/o request (read thread) 241\n> requests\, 234202.82 bytes/r\
 , svc: 0.05 secs\, 0.19 msecs/r\, 0.30 max\n> msecs\n> I/O thread 3 state: 
 waiting for i/o request (read thread) 17 requests\,\n> 126253.18 bytes/r\, 
 svc: 0.00 secs\, 0.14 msecs/r\, 0.29 max msecs\n> I/O thread 4 state: waiti
 ng for i/o request (read thread) 11 requests\,\n> 81920.00 bytes/r\, svc: 0
 .00 secs\, 0.10 msecs/r\, 0.21 max msecs\n> I/O thread 5 state: waiting for
  i/o request (read thread) 5 requests\,\n> 88473.60 bytes/r\, svc: 0.00 sec
 s\, 0.11 msecs/r\, 0.24 max msecs\n> I/O thread 6 state: waiting for i/o re
 quest (read thread) 0 requests\,\n> 0.00 bytes/r\, svc: 0.00 secs\, 0.00 ms
 ecs/r\, 0.00 max msecs\n> I/O thread 7 state: waiting for i/o request (read
  thread) 4 requests\,\n> 61440.00 bytes/r\, svc: 0.00 secs\, 0.07 msecs/r\,
  0.13 max msecs\n> I/O thread 8 state: waiting for i/o request (read thread
 ) 4 requests\,\n> 86016.00 bytes/r\, svc: 0.00 secs\, 0.09 msecs/r\, 0.19 m
 ax msecs\n> I/O thread 9 state: waiting for i/o request (read thread) 5 req
 uests\,\n> 137625.60 bytes/r\, svc: 0.00 secs\, 0.15 msecs/r\, 0.19 max mse
 cs\n> I/O thread 10 state: waiting for i/o request (write thread) 73\n> req
 uests\, 234762.52 bytes/r\, svc: 0.03 secs\, 0.48 msecs/r\, 3.03 max\n> mse
 cs\n> I/O thread 11 state: waiting for i/o request (write thread) 51\n> req
 uests\, 396428.55 bytes/r\, svc: 0.05 secs\, 0.89 msecs/r\, 2.96 max\n> mse
 cs\n> I/O thread 12 state: waiting for i/o request (write thread) 45\n> req
 uests\, 336782.22 bytes/r\, svc: 0.04 secs\, 0.80 msecs/r\, 3.15 max\n> mse
 cs\n> I/O thread 13 state: waiting for i/o request (write thread) 36\n> req
 uests\, 277617.78 bytes/r\, svc: 0.03 secs\, 0.70 msecs/r\, 2.91 max\n> mse
 cs\n> I/O thread 14 state: waiting for i/o request (write thread) 31\n> req
 uests\, 244174.45 bytes/r\, svc: 0.02 secs\, 0.58 msecs/r\, 2.38 max\n> mse
 cs\n> I/O thread 15 state: waiting for i/o request (write thread) 26\n> req
 uests\, 175182.77 bytes/r\, svc: 0.01 secs\, 0.54 msecs/r\, 2.90 max\n> mse
 cs\n> I/O thread 16 state: waiting for i/o request (write thread) 25\n> req
 uests\, 204472.32 bytes/r\, svc: 0.01 secs\, 0.51 msecs/r\, 2.52 max\n> mse
 cs\n> I/O thread 17 state: waiting for i/o request (write thread) 26\n> req
 uests\, 349735.38 bytes/r\, svc: 0.02 secs\, 0.71 msecs/r\, 2.29 max\n> mse
 cs\n>\n>\n> --\n> Mark Callaghan\n> mdcallag@xxxxxxxxx\n>\n> ______________
 _________________________________\n> Mailing list: https://launchpad.net/~p
 ercona-discussion\n> Post to     : percona-discussion@xxxxxxxxxxxxxxxxxxx\n
 > Unsubscribe : https://launchpad.net/~percona-discussion\n> More help   : 
 https://help.launchpad.net/ListHelp\n>\n>\nView your event at http://www.go
 ogle.com/calendar/event?action=VIEW&eid=ODVpYWU4NHViZTFicjA0cW4zazNua2U0ZzA
 gcGVyY29uYS1kaXNjdXNzaW9uQGxpc3RzLmxhdW5jaHBhZC5uZXQ&tok=MzEjYWxla3NhbmRyLm
 t1em1pbnNreUBwZXJjb25hLmNvbTgwNWY3YzJmNjc0ZDMwMWEyNDhhYjlmNjI1ZGVhYWY3NTYyY
 2NjMzE&ctz=Europe%2FKiev&hl=en_GB.
LAST-MODIFIED:20090824T112418Z
LOCATION:
SEQUENCE:2
STATUS:CONFIRMED
SUMMARY:[Percona-discussion] patch for more InnoDB disk IO status in SHOW I
 NNODB STATUS with 5.0.84 percona high perf build 18
TRANSP:OPAQUE
CATEGORIES:http://schemas.google.com/g/2005#event
END:VEVENT
END:VCALENDAR

Attachment: invite.ics
Description: application/ics