users@grizzly.java.net

RE: Selectors threads statistics

From: Meltser Tiran <Tiran.Meltser_at_comverse.com>
Date: Tue, 8 Sep 2015 16:30:53 +0000

Hi Alexey,
We are stuck with all the area of the selectors threads and we suspect we might have a tuning (or other) problem there, would appreciate your advice of the questions below.

Tiran Meltser
System Architect
Global Products & Operations
Comverse - Making Your Network Smarter

T +972-3-7678381
M +972-54-5639381
Tiran.Meltser_at_comverse.com <mailto:Tiran.Meltser_at_comverse.com>
www.comverse.com<http://www.comverse.com/>
P Please think of the environment before printing this email

From: Ben-Yosef Efrat [mailto:Efrat.Ben-Yosef_at_comverse.com]
Sent: Thursday, September 03, 2015 5:08 PM
To: users_at_grizzly.java.net
Subject: RE: Selectors threads statistics

Also,
Even if I set something on the selcetors, like setMaxPoolSize() for example, I always see only 12 selector threads running:
[cid:image001.jpg_at_01D0EA6A.9A705370]

Am I configuring it wrong? 12 threads are not enough for our application.

Thanks
Efrat

From: Ben-Yosef Efrat
Sent: Tuesday, September 01, 2015 1:01 PM
To: users_at_grizzly.java.net<mailto:users_at_grizzly.java.net>
Subject: Selectors threads statistics

Hi Alexey,

Is it possible to add the selectors threads statistics (num of busy, allocated etc.) to the current externalized KPIs (like the workers threads have)?
We see improvements when working with the SameThread IO strategy (instead of the default of worker thread) and we would like to see if tuning is needed, monitor the active threads etc.

Thanks
Efrat
________________________________
"This e-mail message may contain confidential, commercial or privileged information that constitutes proprietary information of Comverse Inc. or its subsidiaries. If you are not the intended recipient of this message, you are hereby notified that any review, use or distribution of this information is absolutely prohibited and we request that you delete all copies and contact us by e-mailing to: security_at_comverse.com<mailto:security_at_comverse.com>. Thank You."
________________________________
"This e-mail message may contain confidential, commercial or privileged information that constitutes proprietary information of Comverse Inc. or its subsidiaries. If you are not the intended recipient of this message, you are hereby notified that any review, use or distribution of this information is absolutely prohibited and we request that you delete all copies and contact us by e-mailing to: security_at_comverse.com. Thank You."




image001.jpg
(image/jpeg attachment: image001.jpg)