[MCOL-4941] Use threadpool for all threads in PrimProc Created: 2021-12-07 Updated: 2023-11-21 Resolved: 2023-10-27 |
|
| Status: | Closed |
| Project: | MariaDB ColumnStore |
| Component/s: | PrimProc |
| Affects Version/s: | 6.2.1 |
| Fix Version/s: | 23.10 |
| Type: | Task | Priority: | Minor |
| Reporter: | David Hall (Inactive) | Assignee: | Leonid Fedorov |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Epic/Theme: | Performance |
| Description |
|
Thread pools should be used for all short lived threads. There are some places in PrimProc where we create new threads: BPPSendThread creates a thread during construction. This happens once per query. These threads should be part of thread pool for efficiency's sake. Perhaps they could share the fServerPool with connections, or maybe make another pool. |
| Comments |
| Comment by Roman [ 2022-02-22 ] |
|
Agree. It is important for loadBlockAsync in the first place. |
| Comment by ziyitan [ 2023-08-25 ] |
|
I want to work on it. |