-
Notifications
You must be signed in to change notification settings - Fork 72
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature Request: Thread Affinity #476
Comments
We can add an callback to the env "on_thread_starts" and call it with the relevant parameters , the user will need to implement the callback and change the attributes of the thread. |
Thank you! |
Passed perf tests |
Hi Developers!
We are building a new application on top of high performance storage products, NVMe SSDs for example along with RocksDB. To fully utilize potentials of the hardware, we are using a Thread-per-Core model, similar to SPDK, Seastar and Glommio, meaning we need to dedicate a few cores to them.
After investigation, we see two options: isolcpus and thread-affinity. We rule out the former as it is not flexible enough and does not meet deployment requirements. RocksDB is extensible through Env, where Filesystem, etc are abstracted. Unfortunately, I do not see a good place to plug thread affinity in.
A preliminary attempt is made here.
The text was updated successfully, but these errors were encountered: