:
- between 1 and 5 seconds : n1
- between 6 and 15 seconds : n2
...
- more than nnn seconds : nx (subject to client timeout, so error in
the log)
On 28.03.2018 13:13, PANG J. wrote:
As shown below,
Last day total requests are 42,368,982, not all are successful, but
42,362,363 are right.
The
As shown below,
Last day total requests are 42,368,982, not all are successful, but
42,362,363 are right.
The failed requests are timeout.
Thanks.
On 2018/3/28 星期三 PM 6:37, André Warnier (tomcat) wrote:
On 28.03.2018 12:31, PANG J. wrote:
what the client I meant is mobile App.
mobile
I do think it's a client timeout.
regards.
On 2018/3/28 星期三 PM 6:37, André Warnier (tomcat) wrote:
Ok. But it is very likely that your "mobile app SDK", also has a timeout
after it sends a request to a server. Or are you /sure/ that it waits
forever ?
/Precisely what/ makes you think that i
what the client I meant is mobile App.
mobile App gets the result from server via SDK.
in future we may move the computing task into App itself.
But currently they are running on server side.
thanks.
On 2018/3/28 星期三 PM 6:11, André Warnier (tomcat) wrote:
I believe that the timeout which Pang J
On 2018/3/28 星期三 AM 10:41, Jie Gao wrote:
To start with, is your hosting machine running out of resources (CPU cycles, memory, etc)?
No. resources are enough. we have about 100 servers for computing, each
with 24 physical cores. But yes, the system load most time is high.
And what is t
Hi,
what the primary reason is handler computes for long time, so client
gets timeout.
On 2018/3/28 星期三 AM 10:08, Jie Gao wrote:
* PANG J. wrote:
Date: Wed, 28 Mar 2018 09:30:17 +0800
From: "PANG J."
To: modperl@perl.apache.org
Subject: handler timeout
User-Agent: Mozilla/5.
Hi,
there are a lot of Floating point operations in my modperl handlers.
(i.e, considering something like OpenPose).
the client is easy to get timeout from the server.
how to fix up this?
Thanks.
