-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Single write optimization #36
Comments
Major commit() overhead is dealing with index. If you don't index symbols performance should improve. Commit() is also not optimised to be called frequently but it should be better once indexing is switched off. |
Thx. Remove indexing from configuration helped a bit. Do you have any plans to add separate implementation of Writer which will be optimized for frequent commits? |
Yes, absolutely. This is a very frequent pattern and it should be optimal and GC free. |
Hi.
I have HA requirements similar to #29. To achieve HA I'm going to write persistent log into nfsdb and replicate it. I will write 99% of time and read 1%. So my main criterion is write performance. I should not lose any data during active node failure so I think the best option for me to commit(persist+replicate) data after every append.
I took SimplestAppend.java as a foundation.
Results:
I changed this tests slightly (commit after every append):
Results:
Is there any way to reduce garbage and improve performance for single append/commit approach?
Thank you.
The text was updated successfully, but these errors were encountered: