Hi,

Your server most probably can handle the load. It depends of course on how
intensive the processing is. The kind of error you are getting (port 80 **** Hit
EOF while fetching headers) suggests that the problem is not in Django but in
Apache, or maybe you are hitting some operating system limit. However nothing is
certain without more information.

If you haven't already done so, you should configure Apache and syslog to use a
timestamp that is accurate to the microsecond. You can then check to see other
log files such as /var/log/syslog (assuming Linux) to see whether they have more
information than the apache log at the exact time the error occurs.

Given that this is most probably not a Django issue but an Apache issue or an
operating system issue, you may be able to get better help elsewhere, for
example in serverfault.com.

Regards,

A.

Antonis Christofides
http://djangodeployment.com



On 2017-05-03 02:31, zhenwuhe0...@gmail.com wrote:
>
> Thanks for your response. 
>
> Our server has 24 Cores and 192G memory, should be big enough to handle this
> kind of load? BTW, one more thing I want to mention is that we are using host
> based docker, possible any config or limitation there?
>
> thanks again.
>
>
> On Monday, May 1, 2017 at 11:06:39 PM UTC-7, Antonis Christofides wrote:
>
>     Hi,
>
>     With an average of 150 requests per second, it is likely that your server
>     is overloaded. You need to examine the available memory and CPU usage.
>
>     Regards,
>
>     A.
>
>     Antonis Christofides
>     http://djangodeployment.com
>
>     On 2017-05-01 22:53, zhenwu...@gmail.com <javascript:> wrote:
>>
>>     Hi, Experts:
>>
>>     We built our system using apache + django and we have lots of clients
>>     sending updates to our backend server at around 1min interval. But we do
>>     have 9000 around devices. From time to time, we are seeing port 80 ****
>>     Hit EOF while fetching headers in apache log or 500 error, could anybody
>>     tell me what does this mean and what maybe the possible reason to cause
>>     this? or any suggestion what I could do to isolate what cause this issue.
>>
>>     thanks in advance.
>>
>>
>>     -- 
>>     You received this message because you are subscribed to the Google Groups
>>     "Django users" group.
>>     To unsubscribe from this group and stop receiving emails from it, send an
>>     email to django-users...@googlegroups.com <javascript:>.
>>     To post to this group, send email to django...@googlegroups.com
>>     <javascript:>.
>>     Visit this group at https://groups.google.com/group/django-users
>>     <https://groups.google.com/group/django-users>.
>>     To view this discussion on the web visit
>>     
>> https://groups.google.com/d/msgid/django-users/5072b5af-5f78-4b75-83af-70da26bff125%40googlegroups.com
>>     
>> <https://groups.google.com/d/msgid/django-users/5072b5af-5f78-4b75-83af-70da26bff125%40googlegroups.com?utm_medium=email&utm_source=footer>.
>>     For more options, visit https://groups.google.com/d/optout
>>     <https://groups.google.com/d/optout>.
>
> -- 
> You received this message because you are subscribed to the Google Groups
> "Django users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to django-users+unsubscr...@googlegroups.com
> <mailto:django-users+unsubscr...@googlegroups.com>.
> To post to this group, send email to django-users@googlegroups.com
> <mailto:django-users@googlegroups.com>.
> Visit this group at https://groups.google.com/group/django-users.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-users/4d62efaf-654b-40ff-a895-efcb1bf2a7e8%40googlegroups.com
> <https://groups.google.com/d/msgid/django-users/4d62efaf-654b-40ff-a895-efcb1bf2a7e8%40googlegroups.com?utm_medium=email&utm_source=footer>.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/6ba224f7-8134-89e6-241c-21e0d88f8291%40djangodeployment.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to