Skip to content
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

os/bluestore: multithreaded '_kv_sync_thread' #10856

Closed

Conversation

tanghaodong25
Copy link
Contributor

Signed-off-by: Haodong Tang haodong.tang@intel.com

Signed-off-by: Haodong Tang <haodong.tang@intel.com>
@liewegas
Copy link
Member

liewegas commented Sep 1, 2016

Did you observe a performance improvement with this? I'm not sure that mulitple kv commit htreads is the way to go... it seems like it won't help too much given the way that rocksdb blocks it's commits (only one in flight to disk at a time, I think).

Also, I think we want to do something a bit different: ensure that each TransContext is submitted in its own thread, and the kv_sync_thread just loops and pushes them to stable storage.

@tanghaodong25
Copy link
Contributor Author

@liewegas There is performance improvement just when changing rocksdb to memdb. @majianpeng made more effort on optimizing multi-transaction-submission with a new PR #11189 . So I close it.

@tanghaodong25 tanghaodong25 deleted the multi-transaction-wip branch October 31, 2016 09:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
4 participants