Backend is uwsgi TCP protocol.
Thanks for your clarify. I am understanding now, Thread pool should
not useful to improve my case.
On Tue, Jun 30, 2015 at 5:17 PM, Lukas Tribus wrote:
>> Hi All:
>> I am using Nginx as a reverse proxy which provide a web API (HTTP GET
>> ) to client.
>> and the bac
> Hi All:
> I am using Nginx as a reverse proxy which provide a web API (HTTP GET
> ) to client.
> and the backend application will get request from nginx and do some
> time-consuming processing (1-2 seconds) then response result to nginx,
> Nginx return result to client.
> I think this is synchron
Hi,
This is what they have to say about threads :
Offloading read operations to the thread pool is a technique applicable to
very specific tasks. It is most useful where the volume of frequently
requested content doesn’t fit into the operating system’s VM cache. This
might be the case with, for
Hi All:
I am using Nginx as a reverse proxy which provide a web API (HTTP GET
) to client.
and the backend application will get request from nginx and do some
time-consuming processing (1-2 seconds) then response result to nginx,
Nginx return result to client.
I think this is synchronize operation.
