Re: PHP Performance/Scalability

Hello

When we throw 5 to 10 concurrent requests/sec, the response times are in ms
for php as well as java. As we increase the load to 1500 concurrent users
for php, the response times climb to 2-3 seconds. We would like to serve
6000+ concurrent users with millisecond response times for php (same as
java).

Thanks.


Deepak
"The greatness of a nation can be judged by the way its animals are treated
- Mahatma Gandhi"

+91 73500 12833
[email protected]

Facebook: https://www.facebook.com/deicool
LinkedIn: www.linkedin.com/in/deicool

"Plant a Tree, Go Green"

Make In India : http://www.makeinindia.com/home


On Tue, Oct 26, 2021 at 3:48 PM shiplu <[email protected]> wrote:

> > Average Response Time for PHP pages is 2-3 seconds for 1500 concurrent
> users (150 requests/sec).
>
> This is where the problem lies. The requests are not being finished and
> then new requests are coming in. The requests are not being finished
> because the first request is slow.
>
> What is the average response time when you send 5 concurrent requests? Is
> it sub 200ms?
>
> How many users do you want to serve in how many seconds?
>
> ―
> Shiplu.Mokadd.im
> Senior Unix Hacker
>
> *Innovation distinguishes between follower and leader*
> —  Steve Jobs
>
>
> *An expert is a person who has made all the mistakes that can be made in a
> very narrow field.*—  Niels Bohr
>
>
> On Tue, Oct 26, 2021 at 12:10 PM Deepak Goel <[email protected]> wrote:
>
>> Hello
>>
>> 1. Concurrent php requests/sec is 150.
>>
>> 2. Average Response Time for PHP pages is 2-3 seconds for 1500 concurrent
>> users (150 requests/sec). If we increase the load beyond 1500 concurrent
>> users, the response time goes up to 10 seconds for 2000+ concurrent  users.
>> We also start getting 500 errors as we increase the load beyond 2000
>> concurrent users.
>>
>> 3. For Java, the response times are in milliseconds even for 6000+
>> concurrent users (for the same functionality)
>>
>> Cheers!
>>
>> Deepak
>> "The greatness of a nation can be judged by the way its animals are
>> treated - Mahatma Gandhi"
>>
>> +91 73500 12833
>> [email protected]
>>
>> Facebook: https://www.facebook.com/deicool
>> LinkedIn: www.linkedin.com/in/deicool
>>
>> "Plant a Tree, Go Green"
>>
>> Make In India : http://www.makeinindia.com/home
>>
>>
>> On Tue, Oct 26, 2021 at 3:28 PM shiplu <[email protected]> wrote:
>>
>>> Hello Deepak,
>>>
>>> 1500 as concurrency is very very high. It means there are 1500 *ongoing*
>>> HTTP requests. They started and didn't finish yet at the same time. This
>>> can only happen when your average response time is high. What is your
>>> average response time?
>>>
>>> ―
>>> Shiplu.Mokadd.im
>>> Senior Unix Hacker
>>>
>>> Meeting Calendar: https://calendar.x.ai/shiplu
>>>
>>> *Innovation distinguishes between follower and leader*
>>> —  Steve Jobs
>>>
>>>
>>> *An expert is a person who has made all the mistakes that can be made in
>>> a very narrow field.*—  Niels Bohr
>>>
>>>
>>> On Tue, Oct 26, 2021 at 11:55 AM Deepak Goel <[email protected]> wrote:
>>>
>>>> Hello
>>>>
>>>> I have a very simple PHP application which I develop on
>>>> Apache-Web-Server. However the application does not scale beyond 1500
>>>> concurrent users (150 requests/sec), even though there is plenty of
>>>> hardware available (CPU is getting utilized 15%, Memory is getting utilized
>>>> 15%).
>>>>
>>>> On a similar note, when I develop the same application in Java, it
>>>> scales to more than 6000 concurrent users (600 requests/sec) on the same
>>>> hardware.
>>>>
>>>> Any pointers on how to address this scalability issue?
>>>>
>>>> Thanks!
>>>>
>>>> Deepak
>>>> "The greatness of a nation can be judged by the way its animals are
>>>> treated - Mahatma Gandhi"
>>>>
>>>> +91 73500 12833
>>>> [email protected]
>>>>
>>>> Facebook: https://www.facebook.com/deicool
>>>> LinkedIn: www.linkedin.com/in/deicool
>>>>
>>>> "Plant a Tree, Go Green"
>>>>
>>>> Make In India : http://www.makeinindia.com/home
>>>>
>>>