Simultaneous Users / Transactions

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

Simultaneous Users / Transactions

Fady Haikal
Hi Team,
I need to know if Tomcat can handle around 2000 concurent user, 17000
number of simultaneouse transactions peak per 10 minutes, assuming the
application can handle them, in additional i need to know what is the
recommended configuration for Tomcat in order to handle this number of
requests.

Regards,
Fady
Reply | Threaded
Open this post in threaded view
|

Re: Simultaneous Users / Transactions

markt
On 19/06/17 10:06, Fady Haikal wrote:
> Hi Team,
> I need to know if Tomcat can handle around 2000 concurent user, 17000
> number of simultaneouse transactions peak per 10 minutes, assuming the
> application can handle them, in additional i need to know what is the
> recommended configuration for Tomcat in order to handle this number of
> requests.

Tomcat will easily handle this. The limiting factor will be the
application and/or the hardware you are running on.

How can 2000 concurrent users generate 17000 simultaneous transactions?

Regarding configuration, the factors you need to consider are:
- concurrent connections (active and inactive)
- concurrent active connections (i.e. actively processing a request)
- new requests made per second
- average time taken to process a request

Depending on the answers, the default configuration may be sufficient.

The alert reader may have noticed that at least one of the factors above
can be derived from the others. This is deliberate. I want to see if the
answers provide are internally consistent.

Mark

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Simultaneous Users / Transactions

Fady Haikal
- Concurrent active connections: 3000
- Concurent passive connections: 1000
- concurrent active connections (i.e. actively processing a request): 1000
- new requests made per second: 28
- average time taken to process a request: 2 - 3 seconds

On Mon, Jun 19, 2017 at 12:46 PM, Mark Thomas <[hidden email]> wrote:

> On 19/06/17 10:06, Fady Haikal wrote:
> > Hi Team,
> > I need to know if Tomcat can handle around 2000 concurent user, 17000
> > number of simultaneouse transactions peak per 10 minutes, assuming the
> > application can handle them, in additional i need to know what is the
> > recommended configuration for Tomcat in order to handle this number of
> > requests.
>
> Tomcat will easily handle this. The limiting factor will be the
> application and/or the hardware you are running on.
>
> How can 2000 concurrent users generate 17000 simultaneous transactions?
>
> Regarding configuration, the factors you need to consider are:
> - concurrent connections (active and inactive)
> - concurrent active connections (i.e. actively processing a request)
> - new requests made per second
> - average time taken to process a request
>
> Depending on the answers, the default configuration may be sufficient.
>
> The alert reader may have noticed that at least one of the factors above
> can be derived from the others. This is deliberate. I want to see if the
> answers provide are internally consistent.
>
> Mark
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>
Reply | Threaded
Open this post in threaded view
|

Re: Simultaneous Users / Transactions

markt
On 19/06/17 10:53, Fady Haikal wrote:
> - Concurrent active connections: 3000
> - Concurent passive connections: 1000
> - concurrent active connections (i.e. actively processing a request): 1000
> - new requests made per second: 28
> - average time taken to process a request: 2 - 3 seconds

Those numbers don't add up.

28 new requests per second with an average processing time of 2-3
seconds gives a figure for concurrent active connections of 56-84.

The default Tomcat configuration will easily handle 3000 concurrent
connections with ~100 active at any one time.

Mark


>
> On Mon, Jun 19, 2017 at 12:46 PM, Mark Thomas <[hidden email]> wrote:
>
>> On 19/06/17 10:06, Fady Haikal wrote:
>>> Hi Team,
>>> I need to know if Tomcat can handle around 2000 concurent user, 17000
>>> number of simultaneouse transactions peak per 10 minutes, assuming the
>>> application can handle them, in additional i need to know what is the
>>> recommended configuration for Tomcat in order to handle this number of
>>> requests.
>>
>> Tomcat will easily handle this. The limiting factor will be the
>> application and/or the hardware you are running on.
>>
>> How can 2000 concurrent users generate 17000 simultaneous transactions?
>>
>> Regarding configuration, the factors you need to consider are:
>> - concurrent connections (active and inactive)
>> - concurrent active connections (i.e. actively processing a request)
>> - new requests made per second
>> - average time taken to process a request
>>
>> Depending on the answers, the default configuration may be sufficient.
>>
>> The alert reader may have noticed that at least one of the factors above
>> can be derived from the others. This is deliberate. I want to see if the
>> answers provide are internally consistent.
>>
>> Mark
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [hidden email]
>> For additional commands, e-mail: [hidden email]
>>
>>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Simultaneous Users / Transactions

Fady Haikal
@Mark, we have 3rd parties and applications that are connecting to the
Tomcat server (not only the users) that will made these transactions

On Mon, Jun 19, 2017 at 12:58 PM, Mark Thomas <[hidden email]> wrote:

> On 19/06/17 10:53, Fady Haikal wrote:
> > - Concurrent active connections: 3000
> > - Concurent passive connections: 1000
> > - concurrent active connections (i.e. actively processing a request):
> 1000
> > - new requests made per second: 28
> > - average time taken to process a request: 2 - 3 seconds
>
> Those numbers don't add up.
>
> 28 new requests per second with an average processing time of 2-3
> seconds gives a figure for concurrent active connections of 56-84.
>
> The default Tomcat configuration will easily handle 3000 concurrent
> connections with ~100 active at any one time.
>
> Mark
>
>
> >
> > On Mon, Jun 19, 2017 at 12:46 PM, Mark Thomas <[hidden email]> wrote:
> >
> >> On 19/06/17 10:06, Fady Haikal wrote:
> >>> Hi Team,
> >>> I need to know if Tomcat can handle around 2000 concurent user, 17000
> >>> number of simultaneouse transactions peak per 10 minutes, assuming the
> >>> application can handle them, in additional i need to know what is the
> >>> recommended configuration for Tomcat in order to handle this number of
> >>> requests.
> >>
> >> Tomcat will easily handle this. The limiting factor will be the
> >> application and/or the hardware you are running on.
> >>
> >> How can 2000 concurrent users generate 17000 simultaneous transactions?
> >>
> >> Regarding configuration, the factors you need to consider are:
> >> - concurrent connections (active and inactive)
> >> - concurrent active connections (i.e. actively processing a request)
> >> - new requests made per second
> >> - average time taken to process a request
> >>
> >> Depending on the answers, the default configuration may be sufficient.
> >>
> >> The alert reader may have noticed that at least one of the factors above
> >> can be derived from the others. This is deliberate. I want to see if the
> >> answers provide are internally consistent.
> >>
> >> Mark
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: [hidden email]
> >> For additional commands, e-mail: [hidden email]
> >>
> >>
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>
Reply | Threaded
Open this post in threaded view
|

Re: Simultaneous Users / Transactions

markt
On 19/06/17 11:08, Fady Haikal wrote:
> @Mark, we have 3rd parties and applications that are connecting to the
> Tomcat server (not only the users) that will made these transactions

Then you need to answer the original questions for ALL user agents.

Mark


>
> On Mon, Jun 19, 2017 at 12:58 PM, Mark Thomas <[hidden email]> wrote:
>
>> On 19/06/17 10:53, Fady Haikal wrote:
>>> - Concurrent active connections: 3000
>>> - Concurent passive connections: 1000
>>> - concurrent active connections (i.e. actively processing a request):
>> 1000
>>> - new requests made per second: 28
>>> - average time taken to process a request: 2 - 3 seconds
>>
>> Those numbers don't add up.
>>
>> 28 new requests per second with an average processing time of 2-3
>> seconds gives a figure for concurrent active connections of 56-84.
>>
>> The default Tomcat configuration will easily handle 3000 concurrent
>> connections with ~100 active at any one time.
>>
>> Mark
>>
>>
>>>
>>> On Mon, Jun 19, 2017 at 12:46 PM, Mark Thomas <[hidden email]> wrote:
>>>
>>>> On 19/06/17 10:06, Fady Haikal wrote:
>>>>> Hi Team,
>>>>> I need to know if Tomcat can handle around 2000 concurent user, 17000
>>>>> number of simultaneouse transactions peak per 10 minutes, assuming the
>>>>> application can handle them, in additional i need to know what is the
>>>>> recommended configuration for Tomcat in order to handle this number of
>>>>> requests.
>>>>
>>>> Tomcat will easily handle this. The limiting factor will be the
>>>> application and/or the hardware you are running on.
>>>>
>>>> How can 2000 concurrent users generate 17000 simultaneous transactions?
>>>>
>>>> Regarding configuration, the factors you need to consider are:
>>>> - concurrent connections (active and inactive)
>>>> - concurrent active connections (i.e. actively processing a request)
>>>> - new requests made per second
>>>> - average time taken to process a request
>>>>
>>>> Depending on the answers, the default configuration may be sufficient.
>>>>
>>>> The alert reader may have noticed that at least one of the factors above
>>>> can be derived from the others. This is deliberate. I want to see if the
>>>> answers provide are internally consistent.
>>>>
>>>> Mark
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: [hidden email]
>>>> For additional commands, e-mail: [hidden email]
>>>>
>>>>
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [hidden email]
>> For additional commands, e-mail: [hidden email]
>>
>>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]