ThreadPool: make high priority tickets enabled by default in PS 5.5

Registered by Alexey Kopytov on 2013-12-01

Benchmarks show that the high priority tickets idea implemented
previously
(https://blueprints.launchpad.net/percona-server/+spec/priority-scheduling-for-threadpool)
is universal enough to be enabled by default.

That is, the default thread pool behavior should be to always put events
from already started transactions into the high priority queue, as we
believe that results in better performance in vast majority of
cases.

One way to achieve that and keep the current semantics for
--thread-pool-high-prio-tickets at the same time is to make the maximum
possible value (UINT_MAX) a new default instead of 0. This way the old
default behavior can be restored by setting the variable to 0, which
disables the high priority queue.

Blueprint information

Status:
Complete
Approver:
Alexey Kopytov
Priority:
High
Drafter:
Alexey Kopytov
Direction:
Approved
Assignee:
Alexey Kopytov
Definition:
Approved
Series goal:
Accepted for 5.5
Implementation:
Implemented
Milestone target:
milestone icon 5.5.35-33.0
Started by
Alexey Kopytov on 2013-12-02
Completed by
Laurynas Biveinis on 2013-12-03

Whiteboard

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.