I think this is where the channel multiplexing will really shine. You could serve large content over one or more channels simultaneously without blocking other channels specifically for messaging/events.
Though one tradeoff I had to decide on was around latency vs throughput over the link. I ended up adding event coalescing as default the protocol. So there's an extra 100 microseconds of latency for significantly better performance on throughput. It can be turned off completely in the dialer options though. So yea, less targeted at gaming or trading.
i probably could help design a scheduler that dynamically tunes according to workload type, using a PID controller to balance the schedule towards throughput vs latency according to the coalescing and the ratio of small frequent packets versus large blobs. more large blobs more often, tune for throughput, more small intermittent messages, tune for latency
a simpler strategy that might work is just shuffling the head of the dispatch queue so little messages packets get spliced finely among the continuous large blobs
nextwave20d ago
mleku20d ago