[MDEV-13077] AliSQL: [Feature] Issue#44 Thread pool Created: 2017-06-13  Updated: 2017-11-17  Resolved: 2017-11-17

Status: Closed
Project: MariaDB Server
Component/s: Server
Fix Version/s: N/A

Type: Task Priority: Major
Reporter: Sergey Vojtovich Assignee: Vladislav Vaintroub
Resolution: Won't Fix Votes: 0
Labels: None

Epic Link: AliSQL patches

 Description    

Description:
 
------------
 
Supply a new thread handing strategy that is pool-of-thread,
 
one-thread-per-connection strategy will create many threads to service connections that
 
clients requested. Not only it has low efficiency, but also cost much CPU time on context switch.
 
 
 
Pool-of-thread only create limited threads to service all connections，and keep the throughput stable
 
no matter how many connection requests.

https://github.com/alibaba/AliSQL/commit/2d6e230073840ed34cd8b74d923a90de6ce99c23

 Comments   
Comment by Sergey Vojtovich [ 2017-10-20 ]

wlad, could you please check if there's still anything of value here?

Comment by Vladislav Vaintroub [ 2017-11-17 ]

This is a copy of Percona's threadpool, which is a copy of MariaDB 5.5 + some of Percona's own features. We have a better implementation of priorization in 10.2.

Percona's pool also has questionable additions in throttling,which can lead to deadlocks. Thus I'd recommend Alibaba to take a look at our implementation rather than using the one in this commit.

Generated at Thu Feb 08 08:02:43 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.