15 karma · joined April 22, 2014
I've built a small project in my spare time, an elo based rating system for MMA fighters. I looked for a bit and haven't find anything of a sort.
Data is sourced from Sherdog.
Any feedback, feature requests or bug reports are appreciated! :)
Thankfully we switched to ninja.
It simply leads to more robust software because compiler rejects large set of incorrect programs that would otherwise end up in production. Your test coverage has to be much larger just to verify that your program is sane on the most basic level.
Rusts compiler is even stricter than most.
Not to mention resilience to change, JS is simply a blunder
It would be fun to run the experiment non the less.
From open(2) man pages on O_DIRECT: Try to minimize cache effects of the I/O to and from this file. In general this will degrade performance, but it is useful in special situations, such as when applications do their own caching. File I/O is done directly to/from user- space buffers
Would using O_DIRECT flag result in similar timings for mmap and read/write?
There is common release process, but with proper infra in place, that shouldn't be a problem.
It takes it 30s, on a decent size codebase, just to tell you that there is "Nothing to do." There is order of magnitude difference between it and make. It's a complete travesty!
O(1) in the paper referred to restructuring, after O( log n ) search time.
We could be violently agreeing, not sure :)
Even if what you meant is expected time complexity for the single insert operation is O(1), that surely cannot be the case. What would be expected time complexity of N inserts then?