Documentation Improvements Needed

[Ryan Lowe]

Current documentation is insufficient. I'll use innodb_ibuf_active_contract as a reference of what I want to see.

***** CURRENT *****

innodb_ibuf_active_contract (default 0) - By default (same to normal InnoDB), the each user threads do nothing about contracting the insert buffer until the insert buffer reaches its maximum size. 1 makes the each user threads positive to contract the insert buffer as possible in asynchronous.

***** PROPOSED *****

innodb_ibuf_active_contract

Version Introduced innodb_io_patches 1.1
Command Line Format --innodb_ibuf_active_contract=[0|1]
Config File Format innodb_ibuf_active_contract
Option Sets Variable Yes, innodb_ibuf_active_contract
Variable Name innodb_ibuf_active_contract
Variable Scope Global
Dynamic Variable Yes
MySQL Binary Compatible Yes
Type boolean
Default 0

By default (same to normal InnoDB), each user threads do nothing about contracting the insert buffer until the insert buffer reaches its maximum size. 1 makes the each user threads positive to contract the insert buffer as possible in asynchronous.

TYPICAL USE CASE

Insert something here about why I'd change this from the innodb default

CALCULATING GOOD VALUES

Although not appropriate here, I'd like to see a (general) approach of how to determine decent starting values

***** END PROPOSED *****

Note that I think this should probably default to 1 :)

[Stewart Smith (stewart)]

percona-patches is no longer being maintained, development has moved to Percona Server. The documentation for Percona Server has seen a lot of work and changes since the days of percona-patches. If there are still documentation gaps, please either re-open against percona-server or file new bugs against Percona Server.

Thanks,
Stewart Smith
Director of Server Development
Percona