Nim 2.x concurrent tail-latency attribution limits between ORC and asyncdispatch
In a Nim 2.x async HTTP service, tail-latency percentiles sometimes degrade only when many requests are in flight. The goal is to attribute those spikes to a specific documented mechanism before tuning the deployment. Two plausible sources are the global ORC cycle-collection pass, which runs under the default memory manager in the 2.x line and has no publish