Pretty pictures of a stuttering server attached.
Notice the CompositingFunctor where ~vector destruction is consuming 30%
of the time, due to ~TemporaryCompositorBuffer taking 27% of the time.
I think we need to move the final buffer release/response logic out of
the compositor thread one way
I think the cleanest solution would be a return to using the "IPC thread
pool" (like in the old days). Presently we use it for receiving
requests, but not for sending responses any more (unless frame dropping).
The challenge is only to ensure we don't reintroduce the problems we
used to have w
