[DOC] Misleading title for write-intensive optimizations page in the manual
Bug #1243067 reported by
Alexey Kopytov
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Percona Server moved to https://jira.percona.com/projects/PS |
Fix Released
|
Medium
|
Hrvoje Matijakovic | ||
5.6 |
Fix Released
|
Medium
|
Hrvoje Matijakovic |
Bug Description
http://
Either fix the URL and the title to something like "write_
Related branches
lp:~hrvojem/percona-server/rn-5.6.14-62.0
- Laurynas Biveinis (community): Approve
-
Diff: 248 lines (+130/-10)9 files modifieddoc/source/conf.py (+1/-1)
doc/source/flexibility/per_query_variable_statement.rst (+43/-0)
doc/source/index.rst (+2/-1)
doc/source/performance/page_cleaner_tuning.rst (+10/-2)
doc/source/performance/xtradb_performance_improvements_for_io-bound_highly-concurrent_workloads.rst (+4/-4)
doc/source/release-notes/Percona-Server-5.6.13-61.0.rst (+2/-2)
doc/source/release-notes/Percona-Server-5.6.14-62.0.rst (+35/-0)
doc/source/release-notes/release-notes_index.rst (+1/-0)
doc/source/scalability/innodb_io.rst (+32/-0)
To post a comment you must log in.
Indeed the title is misleading, but the proposed correction is not fully correct neither: priority refill / innodb_ empty_free_ list_algorithm, thread scheduling priorities, and priority mutexes apply for highly-concurrent I/O-bound RO workloads as well to RW ones. The sync preflush changes are RW-only.
How about "XtraDB Performance Improvements for I/O-Bound Highly-Concurrent Workloads"?