3 ms·
well, you choose the node infrastructure by whatever network latency you need to have guaranteed - obviously public clouds have their limits there.
by m_mueller 6y ago
well, you choose the node infrastructure by whatever network latency you need to have guaranteed - obviously public clouds have their limits there.
- jbverschoor 6y agoBut it’s idiotic to discuss ns-optimizations, when your infrastructure and vms add many times more that. Aws is slow. Not talking about the network.
- m_mueller 6y agoehh I didn't even mention AWS - all I did was using the word 'instance' which seems to have thrown you off.
- LittlePeter 6y agoWhat else can "instance" mean, other than an instance of a virtual server? Granted may not be on AWS, but still is virtual which is a latency killer.
- m_mueller 6y agoIMO you can't automatically go from "we have a latency requirement" to "public cloud is out of the question". It depends on what latency requirement. If you can eat an intermittent delay of 20ms, AWS, to me still seems fine, you just need to plan ahead in terms of what resources you rent there. Between that, and the multiple seconds a GC pause could cost you, there is still a space where GC optimization on AWS would make sense. But if you're in HFT and target micro- or even nanosecond optimizations, you sure don't wanna run anything in that critical path on any public cloud.