Netty Warm Up Stage

[John D. Mitchell]

There's the JVM dynamic compilation / optimization stages and things like the TCP slow-start.

The only way to get over the JVM start up is to run your code for awhile. Given the number of messages you're sending, I think you're doing plenty to warm that part up.

TCP issues are done on a per-connection basis so there's not a lot you can do there unless you can control the settings of the machines on both ends and the routers in between. But at least you can tweak the various settings on the server that your netty code is running on. Alas, there are lots of tradeoffs in this so there's not a simplistic one-size-fits-all answer.

Hope this helps,
John

On Oct 27, 2011, at 11:34 , zx spectrum wrote:

> When I send / receive 10,000,000 messages to try to measure the rate, I see that Netty spends some time to warm up:
>    consuming rate: 64800 messages/s
>    consuming rate: 106016 messages/s
>    consuming rate: 143905 messages/s
>    consuming rate: 177714 messages/s
>    consuming rate: 203981 messages/s  
>    consuming rate: 228632 messages/s
>    consuming rate: 252397 messages/s
>    consuming rate: 272507 messages/s
>    consuming rate: 291819 messages/s
>    consuming rate: 309933 messages/s
> 
> This is the average rate of the messages ( that pass through FrameDecoder ) received per each million.
> 
> Can anybody explain why it happens? And how to eliminate a "warm up" stage?
> 
> Thank you!!
> 
> _______________________________________________
> netty-users mailing list
> netty-users at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/netty-users