-
Notifications
You must be signed in to change notification settings - Fork 339
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
No durability guarantee (benchmark is misleading) #10
Comments
@damnever hi ,thanks your advises, as man2 said about mmap : The file may not actually be updated until msync(2) or munmap(2) is called. Actually i called munmap in this code, so data will be updated. if you can give me your pr to improve it, it will be better;) BTW, about the README i will continue to improve. |
YES, but |
Also, the simple lock cannot fully guarantee the ACID. |
@damnever ,thanks :) |
Still, it is a misleading README, you should remove the benchmark part and all other contents those declares As I mentioned before, you maybe understand the ACID properties, but you implement it wrong, and what is a As a self-learning project is ok, but DO NOT mislead others! |
@damnever thanks to review my README,i have updated the README about the benchmark part and about declares nutsdb is faster than others. About a non-standard transaction or a standard transaction, i mean a transactional database like mysql that provides the ACID properties , i can call it a a standard transaction. If a database not completely including ACID properties,like redis ,i call it a non-standard transaction. if have any question, Welcome to give me advises. BTW, i never want to mislead others. if have any mistake about README or code etc. Welcome to submit issue and give me PR. thanks again! |
I glad to see you make some changes. From the context:
|
@damnever hi, now the master branch of nutsdb has supports persistence , i have use sync function in my code to ensure durability and update the benchmark, selected kvstore which is embedded, persistence and support transactions. benchmark result:
visit https://github.com/xujiajun/nutsdb#benchmarks for detail. |
I didn't go into details, as your benchmark shows, Here is a bit of advice, do some setup and clean up work for each benchmark case. |
@damnever thanks your advice,but i don't know what you mean about doing some setup and cleaning up work for each benchmark case. I have use |
@damnever I think you should be less ambiguous and clearly state the issues. |
@damnever hi, if have no more advises about this issue, i will close it. |
I was wondering why
nutsdb
is so fast, so I did a quick review on your code, and there is no flush/sync call in the code, you should call it to ensure durability and update the benchmark. 💪Also, the README should mention the byte endianness issue as well, and the isolation level is not clear.
The text was updated successfully, but these errors were encountered: