Skip to content
This repository has been archived by the owner on Nov 4, 2024. It is now read-only.

MAP_SYNC destroys performance #7

Open
chloe-alverti opened this issue Aug 21, 2022 · 0 comments
Open

MAP_SYNC destroys performance #7

chloe-alverti opened this issue Aug 21, 2022 · 0 comments

Comments

@chloe-alverti
Copy link

chloe-alverti commented Aug 21, 2022

Hi!

I am running rocksdb on a ext4 dax system in kernel 5.1.
I am testing it with YCSB workloads, and I enable dcpmm wal.
I noticed that the MAP_SYNC flag destroys scalability due to ext4 journaling overheads, and the overall performance is worse than using default rocksdb.

Has anyone else experience this?
Is this expected?

Best Regards,
Chloe

Note: Please use Issues only for bug reports. For questions, discussions, feature requests, etc. post to dev group: https://groups.google.com/forum/#!forum/rocksdb or https://www.facebook.com/groups/rocksdb.dev

Expected behavior

Actual behavior

Steps to reproduce the behavior

@chloe-alverti chloe-alverti changed the title MAP_SYNC destroys performance if not a sync workload MAP_SYNC destroys performance Aug 21, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant