tree aa76584f45cac37214efcc246d0fa20f7336b262
parent 8055f14304bc5505a7b49bfd6142ea53fcc00a17
author Paul J. Davis <paul.joseph.davis@gmail.com> 1359411472 -0600
committer Paul J. Davis <paul.joseph.davis@gmail.com> 1359411472 -0600

Reduce stream message limit

Its possible that a worker is starved out of running during the initial
spin up of worker processes. When there's a high Q running its possible
that a few of the workers are prevented from sending messages back which
ends up causing significant latency as they wait for other workers to
fill up their 100 message buffer and get swapped out.

Once they start sending though the view streams fine. While we don't
understand why some workers behave like this a quick fix is to just
reduce the size of the buffer so that we're not introducing as large of
a delay in the time to first byte.