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

GroupCommit mechanism results in low throughput and inability to fully utilize hardware performance #353

Closed
mzygQAQ opened this issue Feb 2, 2024 · 2 comments

Comments

@mzygQAQ
Copy link
Contributor

mzygQAQ commented Feb 2, 2024

No description provided.

@tabokie
Copy link
Member

tabokie commented Feb 2, 2024

In the early stage of this project, fsync is performed outside the lock. It proves to be inefficient and causes excessive disk IOPS that harms every other I/O task in the system.

Later a proposal was brought up (#258) to parallelize writes in configurable shards. But for our use case (AWS cloud disk), the performance gain is negligible.

@mzygQAQ
Copy link
Contributor Author

mzygQAQ commented Feb 5, 2024

I found that some pingcap boys doing multi wall writing in the blog of Hackathon. Where can I find the relevant codo~

@mzygQAQ mzygQAQ closed this as completed Feb 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants