No performance numbers. No tests. Nothing about how it manages concurrency, how it actually writes to disk, how it does replication.
It appears to be a server not a lib. Why would someone use this instead of kafka?
It appears to be a server not a lib. Why would someone use this instead of kafka?
The README states that replication is not implemented yet. I encourage you to also check this issue https://github.com/phaistos-networks/TANK/issues/14 for some details on the I/O semantics, and the Wiki for answers to other questions: https://github.com/phaistos-networks/TANK/wiki
Network I/O is obviously asynchronous - you may want to check the codebase. Disk I/O is synchronous, but: - uses sendfile() and read readahead() to reduce or eliminate the likelihood of blocking reads: see here please https://github.com/phaistos-networks/TANK/issues/14#issuecom...
- AIO is either broken or supported on XFS (depending on kernel release, and also in the past, appending to a file on an XFS fs could block and degrade performance). But not using DirectI/O so writes end up in memory and only get flushed if it hits the commit count, or periodically - so, particularly for local disks, HDDs or SSDs, this in practice never blocks for more than a few ms when flushing, if at all.
Multithreaded does not mean multiple files.
> But not using DirectI/O so writes end up in memory and only get flushed if it hits the commit count, or periodically - so, particularly for local disks, HDDs or SSDs, this in practice never blocks for more than a few ms when flushing, if at all.
Unless you are actually using it under a high throughput scenario which is why you would use a lib like this. It will work great until you hit the actual flush point, then possibly block for seconds even minutes.
If your performance needs are high, mandating XFS is not unreasonable.
Multiple files does mean multiple threads. Unless you manage to run this without a modern operating system.
That is completely debatable. We are talking about a "a high performance distributed log service". Not a word processor.
> Multiple files does mean multiple threads.
Which is something entirely different from what I said...
If you're not mentioning kernel calls, allocations, thread synchronization, io mechanism etc. you're not going to be very believable.