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

As I mentioned memory access latency - I just posted my old article series about measuring RAM access performance (using different database workloads) to HN and looks like it even made it to the front page (nice):

https://news.ycombinator.com/item?id=25863093



If the problem involves independent traversals, interleaving with coroutines is a practical way to hide latency https://dl.acm.org/doi/10.1145/3329785.3329917 https://www.linkedin.com/pulse/dont-stall-multitask-georgios...


We've made Scylla as async, shared nothing as possible, and we've also started adding C++20 coroutines (to replace futures/promises). We'll be doing more of that in 2021.

https://www.scylladb.com/2021/01/12/making-scylla-a-monstrou...


I plan to test Scylla (and Postgres with TimescaleDB) out soon after done with basic Linux tests :)


Just note that TimescaleDB is olap (columnar compression), scylladb is oltp with async-fsync and Postgresql is disk-fsync-on by default.




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

Search: