3 ms·
Great. I've been wanting something like this for a while. I've got a few questions: 1. How large files are supported? 2. It says that it will only persist pri
by hello_there 11y ago
Great. I've been wanting something like this for a while. I've got a few questions:
1. How large files are supported?
2. It says that it will only persist primitive fields on objects - does that exclude persisting a byte array?
3. What are the failure semantics? For example, what happens if my computer's power supply fails in the middle of a write? How will the program behave the next time it is started?
- javajosh 11y agoGood questions, but wouldn't it be fun to find out the answers using empirical tests? You might even be able to add tests and submit a PR, and be immortalized in the annals of github.
- mrits 11y agoYou don't get things done very fast, do you?
- dang 11y ago> You don't get things done very fast, do you? Please don't make rude comments on Hacker News.
- mrits 11y agoIt is a legitimate response to a problem that plagues the hacker community. Focus on the task at hand. Trying to understand the intricacies of a system can be educational but the best lessons learned are from completing your current project. I'm surrounded by intelligent people that can't get anything done.
- dang 11y agoOk, but the problem with your previous comment wasn't your view, but the rudeness. It's possible to express your view without rudeness; you just did. That's what we're going for here.
- probablyfine 11y agoHi, glad you like it. 1. Under the hood it partitions the log into sections to avoid Java's MappedByteBuffer size-limit. I've not tried to deliberately push the file-size limit yet, but it's something to add to the benchmarks when I publish them (soon!) 2. It doesn't support primitive arrays as of 1.4, but this is something that I have considered in future versions. Pull requests are definitely welcome. 3. I've not tested these failure cases yet.