https://www.nginx.com/blog/inside-nginx-how-we-designed-for-performance-scale/

On Fri, Jan 7, 2022 at 6:33 PM James Read <jamesread5737@gmail.com> wrote:

>
>
> On Fri, Jan 7, 2022 at 11:56 AM Anoop Alias <anoopalias01@gmail.com>
> wrote:
>
>> This basically depends on your hardware and network speed etc
>>
>> Nginx is event-driven and does not fork a separate process for handling
>> new connections which basically makes it different from Apache httpd
>>
>
> Just to be clear Nginx is entirely single threaded?
>
> James Read
>
>
>>
>> On Wed, Jan 5, 2022 at 5:48 AM James Read <jamesread5737@gmail.com>
>> wrote:
>>
>>> Hi,
>>>
>>> I have some questions about Nginx performance. How many concurrent
>>> connections can Nginx handle? What throughput can Nginx achieve when
>>> serving a large number of small pages to a large number of clients (the
>>> maximum number supported)? How does Nginx achieve its performance? Is the
>>> epoll event loop all done in a single thread or are multiple threads used
>>> to split the work of serving so many different clients?
>>>
>>> thanks in advance
>>> James Read
>>> _______________________________________________
>>> nginx mailing list
>>> nginx@nginx.org
>>> http://mailman.nginx.org/mailman/listinfo/nginx
>>
>>
>>
>> --
>> *Anoop P Alias*
>>
>> _______________________________________________
>> nginx mailing list
>> nginx@nginx.org
>> http://mailman.nginx.org/mailman/listinfo/nginx
>
> _______________________________________________
> nginx mailing list
> nginx@nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx



--
*Anoop P Alias*
_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx