2 ms·
In most situations it’s memory bound. In hyper cost savings situations it comes down to the fact that you need to run 3+ nodes at the very least in order to hav
by whalesalad 7y ago
In most situations it’s memory bound. In hyper cost savings situations it comes down to the fact that you need to run 3+ nodes at the very least in order to have some guarantees about data resilience. In reality you usually want more than 3 and you even want multiple clusters of more than 3 nodes each. So it can become costly.
Most people just run one node. It works fine until the node falls over and comes back with zero indexes.
- outworlder 7y ago> Most people just run one node. That's completely unacceptable for any non-toy workloads. If you want a single node, deploy something like PG. You aren't using any of the "Elastic" capabilities, so why bother? If the volume of data is that small, it's better to run 3 small nodes than a single, larger one.