make cassandra io threads configurable #4034
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This commit was authored by @cjcobb23 and has been running in our reporting environments.
High Level Overview of Change
The cassandra driver uses worker threads to process requests. The number of worker threads is configurable, though previously we just set it to
std::thread::hardware_concurrency
. For large machines with many cores, this is probably too much. We noticed on the large machines that under high CPU load, a large majority of the CPU time was spent in system calls. Reducing the number of io threads used by the driver brought the amount of time spent in system calls down. This commit introduces a config option to set the number of io threads, and also changes the default to 4.