3 ms·
Of course. :) I don't mean to imply you weren't working hard or that these bugs were unusual for any complex project. I'm just getting the impression that the
by fweespeech 11y ago
Of course. :)
I don't mean to imply you weren't working hard or that these bugs were unusual for any complex project. I'm just getting the impression that the current version of RethinkDB you end up scaling like this if you were attempting to be safe:
1) Get to 5-9 Nodes
2) Vertically scale this cluster.
3) Shard via adding additional clusters [e.g. 5 Clusters of 7 Nodes] since ~30 nodes for certain workloads you run into performance issues.
- coffeemug 11y agoNot quite true -- there are many deployments with >30 nodes in the wild. Some deployments with >30 nodes did run into issues, but I think a lot of that is extremely user-specific (and if you get to that level, RethinkDB engineers will help with all the custom issues you might run into).
- fweespeech 11y agoFair enough, thanks. :)