Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

webscale specific performance timers and table stats

Description

MyRocks uses webscale specific performance timers. Need to evaluate whether to include in Percona Server, alter to some other form, or eliminate entirely. Search code for MYR-3 comments

See also MYR-13

This impacts the ability to present/expose table stats via the handlerton:

https://blueprints.launchpad.net/percona-server/+spec/myrocks-my-io-perf-5.6
https://blueprints.launchpad.net/percona-server/+spec/myrocks-my-io-perf-5.7

Environment

None

Smart Checklist

Activity

Show:

George Lorch January 9, 2017 at 9:07 PM
Edited

George Lorch December 13, 2016 at 7:51 PM

Laurynas Biveinis December 7, 2016 at 9:19 AM

include/ and mysys/ seem appropriate to me

George Lorch December 6, 2016 at 10:18 PM

Upstream agreed to consider a patch that factors out the my_io_perf* from mysqld.h/cc

I am looking at file naming and wanting to follow MySQL precedent for this type of utility. Since his code is almost totally stand-alone (needs very little of other MySQL code to perform its function) I am looking at ./include/my_io_perf.h and mysys/io_perf.cc

Does this sound like it fits with what you know of server utility internals naming or do you have a better suggestion?

George Lorch November 23, 2016 at 7:55 PM
Edited

Done

Details

Assignee

Reporter

Labels

Components

Fix versions

Priority

Smart Checklist

Created October 5, 2016 at 4:41 AM
Updated December 27, 2018 at 1:42 PM
Resolved January 10, 2017 at 3:58 PM
Configure