https://docs.google.com/document/d/1gCsFxXamW8RRvOe5hECz98Ft...
Perhaps a key difference is this point from the Github document:
"Since the OOBGC runs the GC after the response is finished, it can cause the web worker to take longer in order to be ready to process the next incoming request. This means that clients can suffer from latency due to queuing wait times."
It seems like a little bit more intelligence in the load balancer that sits in front of the application servers would go a long way here. Could it only route requests to servers which have finished garbage collecting and are ready to serve again?