What might be causing increasing latency?

[Sergey S]

Hi

This is quotation of Flash Socket.write* methods description:
Data written by this method is not immediately transmitted; it is queued
until the flush() method is called.



justkevin wrote:
> 
> Thanks for the suggestions-- it turns out the problem was client side, not
> Netty at all. 
> 
> If anyone wants to learn from my mistake:
> 
> After posting I added a ChannelFuture listener object which timed how long
> it took to write, and saw that it was zero. Combined with the fact I knew
> the delay was after the creation of the Pong event almost ruled out
> anything server side.
> 
> I reexamined the client code and found the error. The client processes a
> message frame (length prepended group of messages) when a Flash socket
> fires a SocketData event letting it know some data arrives. The server
> sends one message frame every 200 ms. Each message frame creates a socket
> data event when it arrives.
> 
> Except that pings are processed immediately, so it's possible for a pong
> response to arrive bunched up with another message, creating a backlog.
> The backlogged pong didn't get processed until some other message came in
> after it. Since only pings create a backlog, the problem was caused, and
> exacerbated, by my attempts to measure it.
> 
> 

-- 
View this message in context: http://n2.nabble.com/What-might-be-causing-increasing-latency-tp4269271p4292063.html
Sent from the Netty User Group mailing list archive at Nabble.com.