Add a new screen with InnoDB information like:

• buffer pool (size and # , free pages, dirty pages, Hit Rate...)
• page statistics (Reads, Writes, Created, read/sec, write/sec, create/sec)
• Insert Buffers
• AHI

anything more ?

Hi Lefred,

I have installed the innotopgo version 0.3 tool and it is very helpful

I was testing all the available dashboards by creating the test scenarios, the locking info dashboard is not getting switched post giving the input as , also it is prompting to provide the thread_id as input, post giving the thread_id, it is failing to fetch the locking details

please help to resolve this issue or let me know if I am missing something.

PFA ,

Updated the README.md to include connection instructions for the application. On first use of the app, I expected something like innotop's connection, but had to look at the source code to find the mysql url. Providing this in the README will help prospective users (and may be later a --help/-h switch).

See the help using mmake

$ mmake help

  build      Build executable in current OS
  fmt        format code (default)
  genall     Build all executables
  genlinux   Build Linux executable
  genmac     Build MacOS executable
  genwin     Build Windows executable
  lint       check code for best practices
  vet        Check code for correctness

Get all information possible for a thread.

Check how to add the information returned by:

select *, pps.PROCESSLIST_COMMAND AS command,
                                  pps.THREAD_ID AS thd_id, pps.PROCESSLIST_ID AS conn_id,
                                  conattr_pid.ATTR_VALUE AS pid, pps.PROCESSLIST_STATE AS state,
                                  if((pps.NAME in ('thread/sql/one_connection','thread/thread_pool/tp_one_connection')),
                                   concat(pps.PROCESSLIST_USER,'@',pps.PROCESSLIST_HOST),
                                   replace(pps.NAME,'thread/','')) AS user,
                                  pps.PROCESSLIST_DB AS db, sys.format_statement(pps.PROCESSLIST_INFO) AS current_statement,
                                  if(isnull(esc.END_EVENT_ID), format_pico_time(esc.TIMER_WAIT),NULL) AS statement_latency,
                                  format_pico_time(esc.LOCK_TIME) AS lock_latency,
                                  if(isnull(esc.END_EVENT_ID),esc.TIMER_WAIT,0) AS sort_time
                            from (((((((performance_schema.threads pps
                            left join performance_schema.events_waits_current ewc
                                on((pps.THREAD_ID = ewc.THREAD_ID)))
                            left join performance_schema.events_stages_current estc
                                on((pps.THREAD_ID = estc.THREAD_ID)))
                            left join performance_schema.events_statements_current esc
                                on((pps.THREAD_ID = esc.THREAD_ID)))
                            left join performance_schema.events_transactions_current etc
                                on((pps.THREAD_ID = etc.THREAD_ID)))
                            left join sys.x$memory_by_thread_by_current_bytes mem
                                on((pps.THREAD_ID = mem.thread_id)))
                            left join performance_schema.session_connect_attrs conattr_pid
                                on(((conattr_pid.PROCESSLIST_ID = pps.PROCESSLIST_ID) and (conattr_pid.ATTR_NAME = '_pid'))))
                            left join performance_schema.session_connect_attrs conattr_progname
                                on(((conattr_progname.PROCESSLIST_ID = pps.PROCESSLIST_ID)
                                and (conattr_progname.ATTR_NAME = 'program_name'))))
                            where pps.PROCESSLIST_ID is not null
                              and pps.PROCESSLIST_COMMAND <> 'Daemon'
                              and user <> 'sql/event_scheduler'
                            order by sort_time desc                            

We could also display the list of previous queries in a transaction

Currently, when you are in a different dashboard like or , if you press some keys that have a meaning in the Processlist (main dashboard), once you get back to it (<--) the first element out of the queue is processed and can lead you again to another dashboard, etc...