5 ms·
I think we need to modify the benchmark to give enough time for the RTS to "warmup" before timing max pause times. This will provide a fairer comparison, since
by willsewell 10y ago
I think we need to modify the benchmark to give enough time for the RTS to "warmup" before timing max pause times. This will provide a fairer comparison, since the end goal is to evaluate languages for web servers with large heaps and low latency requirements.
- dilap 10y agoI mean having a short period of time with long latency still sucks though too, right? That's real customers getting real low-quality service. Then maybe you're left doing complex things like running the server with fake traffic as a warming up period to get it to be fast enough. Sure, it'll work, but it's a lot of extra hassle.
- ch4s3 10y agoYou'd probably use load balancing to send some traffic to new images while they warm up. At lower volumes, you shouldn't be hitting GC pauses mid request. Then after a certain point you point everything to the new version. This is good for QA too.
- deleted 10y ago[deleted]
- dilap 10y agodepending on what you're doing, maybe you consider this complexity no big deal. but i don't think, for eaxmple, a standard setup using aws elb and autoscaling would support this.