Re: [jetty-users] CPU spikes caused by Selector threads

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

Re: [jetty-users] CPU spikes caused by Selector threads

From: Greg Wilkins <gregw@xxxxxxxxxxx>
Date: Mon, 30 May 2016 21:33:46 +1000
Delivered-to: jetty-users@xxxxxxxxxxx
List-archive: <https://dev.eclipse.org/mailman/private/jetty-users>
List-help: <mailto:jetty-users-request@eclipse.org?subject=help>
List-subscribe: <https://dev.eclipse.org/mailman/listinfo/jetty-users>, <mailto:jetty-users-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://dev.eclipse.org/mailman/options/jetty-users>, <mailto:jetty-users-request@eclipse.org?subject=unsubscribe>

The selector threads are the threads in jetty 8 that run the NIO Selector. They are responsible for initiating all IO in the server, specifically they initiate all reads and they handle the unblocking of any blocked writes.

If the server is busy, then the selector threads are often busy.

A 100% CPU spike might suggest a bug, but a 65% spike could just be busy IO or even a DOS attack.

Note that jetty-8 is end of life an no longer supported. That release is 3 years old. So updating to a 9.3.x release might be best.

regards

Greg Wilkins <gregw@xxxxxxxxxxx> CTO http://webtide.com

Follow-Ups:
- Re: [jetty-users] CPU spikes caused by Selector threads
  - From: Kohei Nozaki

References:
- [jetty-users] CPU spikes caused by Selector threads
  - From: Kohei Nozaki

Prev by Date: [jetty-users] CPU spikes caused by Selector threads
Next by Date: [jetty-users] Jetty 9.3.x/Windows Security Vulnerability CVE-2016-4800
Previous by thread: [jetty-users] CPU spikes caused by Selector threads
Next by thread: Re: [jetty-users] CPU spikes caused by Selector threads
Index(es):
- Date
- Thread

Breadcrumbs