Questions about ejb waitTime statistic

106 views
Skip to first unread message

omas...@gmail.com

unread,
Feb 7, 2023, 5:09:24 AM2/7/23
to WildFly
I have some questions about the ejb waitTime statistic :

1) I guess the time is in milliseconds and it is a total wait time right ?
2) What could explain that the waitTime is way higher than 0 when peakConcurrentInvocations is way below the poolMaxSize ?

Here is an example:

executionTime : 2702304
invocations : 1657621
peakConcurrentInvocations : 3
poolAvailableCount : 500
poolCreateCount : 3
poolCurrentSize : 3
poolMaxSize : 500
poolName : slsb-strict-max-pool
waitTime : 26617

As you can see the waitTime is quite high (26 seconds) while only having 3 concurrent invocations which is way under the poolMaxSize.

If I divide 'invocations' by 'waitTime' is gives me an average of 62ms which seems quite high to me.

What is exactly included in the computing of the waitTime, so that I could understand where this total of 26s comes from ?

Thanks a lot.

Cheng Fang

unread,
Feb 15, 2023, 11:14:17 AM2/15/23
to omas...@gmail.com, WildFly

On Feb 7, 2023, at 5:09 AM, omas...@gmail.com <omas...@gmail.com> wrote:

I have some questions about the ejb waitTime statistic :

1) I guess the time is in milliseconds and it is a total wait time right ?

Yes.

2) What could explain that the waitTime is way higher than 0 when peakConcurrentInvocations is way below the poolMaxSize ?

To calculate the average wait-time per invocation for this slsb: 

waitTime : 26617 / invocations : 1657621 = 0.0160573496595422 millis per invocation

which is passable.

Only 3 threads are created so far, though the configured max thread pool size is 500, since 3 threads already suffice to handle all invocations.



Here is an example:

executionTime : 2702304
invocations : 1657621
peakConcurrentInvocations : 3
poolAvailableCount : 500
poolCreateCount : 3
poolCurrentSize : 3
poolMaxSize : 500
poolName : slsb-strict-max-pool
waitTime : 26617

As you can see the waitTime is quite high (26 seconds) while only having 3 concurrent invocations which is way under the poolMaxSize.

If I divide 'invocations' by 'waitTime' is gives me an average of 62ms which seems quite high to me.

What is exactly included in the computing of the waitTime, so that I could understand where this total of 26s comes from ?

Thanks a lot.


--
You received this message because you are subscribed to the Google Groups "WildFly" group.
To unsubscribe from this group and stop receiving emails from it, send an email to wildfly+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/wildfly/32a2312e-ecfe-40a9-8de0-c404ec495ddbn%40googlegroups.com.

omas...@gmail.com

unread,
Feb 15, 2023, 1:28:21 PM2/15/23
to WildFly
Thanks for your answer.
My bad, I indeed flipped the numbers by dividing invocations by waitTime instead of dividing waitTime by invocations.
I should have seen it when reviewing my questions. It suddenly makes more sense when doing the math correctly.
I guess I need more sleep :)

Suresh G

unread,
May 9, 2023, 11:47:16 AM5/9/23
to WildFly
Dear All,
Even though i give 10 or 500 or 1000 concurrent request via Jmeter below always stays in 10. Is there any config to be considered?
poolCreateCount : 10
poolCurrentSize : 10

Thanks  

Cheng Fang

unread,
May 9, 2023, 11:58:22 AM5/9/23
to Suresh G, WildFly
Did you configure both /subsystem=ejb3/strict-max-bean-instance-pool=slsb-strict-max-pool and /subsystem=ejb3/thread-pool=default to suitable values?


Reply all
Reply to author
Forward
0 new messages