Hi, On Thu, Jan 21, 2021 at 5:02 PM Abhirama <[email protected]> wrote: > Is my logic there incorrect?
I don't see why, for the exact same operation, Jetty would be slow in one case and fast in another. Which hints that the problem does not lie in Jetty, but perhaps really in the network. Did you take into account TCP slow start? Did you take into account JIT compilation, so that for the first messages the JIT is still compiling, but after a while the code is optimized by the JIT? What you show seems to be a classical case where the server can write faster than the client can read. Do you queue in a tight loop on the server, without waiting for the previous writes to notify the callback? I would look at the client first, what you describe is the classical "client can't keep up with the server" behavior. -- Simone Bordet ---- http://cometd.org http://webtide.com Developer advice, training, services and support from the Jetty & CometD experts. _______________________________________________ jetty-users mailing list [email protected] To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jetty-users
