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

Isn't writing to commit log a bottleneck? #3

Open
veeral-patel opened this issue Mar 23, 2023 · 1 comment
Open

Isn't writing to commit log a bottleneck? #3

veeral-patel opened this issue Mar 23, 2023 · 1 comment

Comments

@veeral-patel
Copy link

veeral-patel commented Mar 23, 2023

let's say we fsync to the FS for every write, for updating commit log.

with thousands or millions or writes per second won't this rapidly bottleneck the number of writes we can handle? in the process it would defeat the point of writing to memory in the first place, no?

sorry if this is a silly question. i'm sure i'm missing something.

@veeral-patel veeral-patel changed the title isn't writing to commit log a bottleneck? Isn't writing to commit log a bottleneck? Mar 23, 2023
@richardartoul
Copy link
Owner

The commitlog isn't stored locally, its written to FDB.

Every commit log entry contains 1000s of 10s of thousand of logical writes so its 1 fsync for every X thousands of writes. In addition, FDB can batch more writes together into one fsync in the tlog processes

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