Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Using your numbers and speaking roughly, if you're doing 50k rps and 500 typically to the same row wasn't your contention around 1%? TigerBeetle clais to be able to handle work loads with very high contention, for example 80 or 90% of transactions filtering out a fee to a single account to make up a use case.


Ah, you might be right!

Contention is what can be parallelized, right?

So with roughly 100-200 requests/s you end up with 1-0.5 contention if I understood that right.

That moves me even further towards agarlands points, though - if I plug that into the equation, I end up with >50k qps.

The used numbers create an insanely distorted idea wrt real world performance




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: