[SERVER-16736] support more than 1 checkpoint thread for WiredTiger Created: 06/Jan/15  Updated: 03/May/23  Resolved: 03/May/23

Status: Closed
Project: Core Server
Component/s: Storage, WiredTiger
Affects Version/s: None
Fix Version/s: None

Type: New Feature Priority: Major - P3
Reporter: Mark Callaghan Assignee: Backlog - Storage Engines Team
Resolution: Won't Do Votes: 3
Labels: wiredtiger
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-16665 WiredTiger b-tree uses too much space... Closed
Related
related to WT-1463 Share CPU overhead of checkpoints Closed
related to WT-1744 Throttle inserts when the cache has l... Closed
Assigned Teams:
Storage Engines
Participants:

 Description   

Discussion started in SERVER-16665. WT supports multiple eviction threads but uses only 1 checkpoint thread. Both eviction and checkpoint threads can do compression when compression is used for a collection/index so more threads for checkpoint is likely to reduce write stalls during slow checkpoints. The wt_perf.c benchmark client uses more than 1 checkpoint thread, so I assume that is supported for WT.



 Comments   
Comment by Daniel Pasette (Inactive) [ 08/Jun/15 ]

We hope this will be addressed by bounding the work we do in a checkpoint. See WT-1744.

Comment by Mark Callaghan [ 06/Jan/15 ]

And if checkpoint cannot be multi-threaded it should still benefit from helper threads to do compression and call pwrite concurrent with other work done by the main checkpoint thread.

Generated at Thu Feb 08 03:42:05 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.