[jetty-users] WebSockets slowness

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

[jetty-users] WebSockets slowness

Patrick Santora
I have a cluster of Jetty 7.x servers running with WebSockets currently, but have noticed that after around 1000 users connect through WebSockets it starts to take longer and longer for new session to connect. I've played around with the Jetty thread pool just for kicks to see what happened with no luck. After perusing the internet for a silver bullet fix I came to the conclusion that I should just talk to the community to see if any one else has ran into similar issues. :)

So my question is in general. Is there a setting I need to keep in mind in order to reach a larger number of connections against a single Jetty server or should I be considering another approach to this dilemma (aka bring up additional servers to lighten the load on each box)?

Any and all help would be appreciated.

Thanks
-Pat

_______________________________________________
jetty-users mailing list
[hidden email]
https://dev.eclipse.org/mailman/listinfo/jetty-users
Reply | Threaded
Open this post in threaded view
|

Re: [jetty-users] WebSockets slowness

Thomas Becker
Hi Patrick,

in general this is a good starting point for you: http://wiki.eclipse.org/Jetty/Howto/High_Load

Regarding your current problem, it's crucial to identify the bottleneck of your setup. First thing to do is to throw some thread dumps during a high load period (kill -3 jetty_pid on *nix). By analyzing the dumps you can see what your threads are busy with and if there's for example some resource contention to a database.
The next step would be some profiling tool like jprofiler or yourkit maybe together with some reproducable loadtests to analyze the problem isolated on a non production server.

Hope that helps a bit.

Cheers,
Thomas

On 2/9/12 4:48 PM, Patrick Santora wrote:
I have a cluster of Jetty 7.x servers running with WebSockets currently, but have noticed that after around 1000 users connect through WebSockets it starts to take longer and longer for new session to connect. I've played around with the Jetty thread pool just for kicks to see what happened with no luck. After perusing the internet for a silver bullet fix I came to the conclusion that I should just talk to the community to see if any one else has ran into similar issues. :)

So my question is in general. Is there a setting I need to keep in mind in order to reach a larger number of connections against a single Jetty server or should I be considering another approach to this dilemma (aka bring up additional servers to lighten the load on each box)?

Any and all help would be appreciated.

Thanks
-Pat


_______________________________________________
jetty-users mailing list
[hidden email]
https://dev.eclipse.org/mailman/listinfo/jetty-users

-- 
thomas becker
[hidden email]

http://webtide.com / http://intalio.com
(the folks behind jetty and cometd)

_______________________________________________
jetty-users mailing list
[hidden email]
https://dev.eclipse.org/mailman/listinfo/jetty-users
Reply | Threaded
Open this post in threaded view
|

Re: [jetty-users] WebSockets slowness

Patrick Santora
Fantastic.

I have a virtual production load that I through against my environment along with both JConsole and YourKit. Thread pools look good on the both, so I will look to talk with my IT guy to see what we can do on an OS level.

Thanks for the rapid response.
-Pat

On Thu, Feb 9, 2012 at 7:57 AM, Thomas Becker <[hidden email]> wrote:
Hi Patrick,

in general this is a good starting point for you: http://wiki.eclipse.org/Jetty/Howto/High_Load

Regarding your current problem, it's crucial to identify the bottleneck of your setup. First thing to do is to throw some thread dumps during a high load period (kill -3 jetty_pid on *nix). By analyzing the dumps you can see what your threads are busy with and if there's for example some resource contention to a database.
The next step would be some profiling tool like jprofiler or yourkit maybe together with some reproducable loadtests to analyze the problem isolated on a non production server.

Hope that helps a bit.

Cheers,
Thomas


On 2/9/12 4:48 PM, Patrick Santora wrote:
I have a cluster of Jetty 7.x servers running with WebSockets currently, but have noticed that after around 1000 users connect through WebSockets it starts to take longer and longer for new session to connect. I've played around with the Jetty thread pool just for kicks to see what happened with no luck. After perusing the internet for a silver bullet fix I came to the conclusion that I should just talk to the community to see if any one else has ran into similar issues. :)

So my question is in general. Is there a setting I need to keep in mind in order to reach a larger number of connections against a single Jetty server or should I be considering another approach to this dilemma (aka bring up additional servers to lighten the load on each box)?

Any and all help would be appreciated.

Thanks
-Pat


_______________________________________________
jetty-users mailing list
[hidden email]
https://dev.eclipse.org/mailman/listinfo/jetty-users

-- 
thomas becker
[hidden email]

http://webtide.com / http://intalio.com
(the folks behind jetty and cometd)

_______________________________________________
jetty-users mailing list
[hidden email]
https://dev.eclipse.org/mailman/listinfo/jetty-users



_______________________________________________
jetty-users mailing list
[hidden email]
https://dev.eclipse.org/mailman/listinfo/jetty-users