4
And if possible how can I extend this time for large queries/requests?
4
And if possible how can I extend this time for large queries/requests?
3
I managed to solve the problem, I changed the max_execution_time
for 900
which is equivalent to 15 minutes and worked!
1 hour for a requisition? #fear
Your reply automatically ended up in the analysis queue as possible low quality because of the size and content. I chose "Looks OK," but it would be nice if you elaborate a little more to avoid this kind of hassle. I would also like to make it clear that it was not I who voted negative.
@Victorstafusa yes, you’re right... but still do not understand the -1
they gave, the answer is right. (are people like this guy who makes the site lose quality)
@Silvioandorinha Hard to understand even. Take my +1 to undo the -1 then.
I gave the -1, the answer itself is right, but I see no justification for a request time as absurd as 1 hour. Is there any possibility that any requisition takes such a long processing time? If yes I recommend you to review the code because such a large query becomes unsustainable.
Reiterating q o -1 was the value adopted, not the response itself.
@Erloncharles yes, I agree that maybe the time of one hour may have been unnecessary but I believe that 15 minutes would be enough for larger queries, but in the answer I only described what I did.. I’ll change it there.
All right, just to remind you that a correct answer doesn’t always mean an efficient one. It can answer the question but can bring other mistakes in the future, it makes a correct answer, but of low quality. I’ll take my -1 and put a +1
fastcgi or uwscgi? If it’s fastcgi, maybe use fastcgi_read_timeout
could help: http://stackoverflow.com/a/17511476/1518921
Browser other questions tagged php mysql nginx
You are not signed in. Login or sign up in order to post.
Error 504 has more to do with the HTTP server or the reverse proxy (Nginx, for example). Could you please detail what these servers or proxies are?
– Leonel Sanches da Silva
@Ciganomorrisonmendez Appears the Nginx also
– Silvio Andorinha
Being fastcgi, I believe it may be an exceeded timeout in the request to the php script, but it’s like @Ciganomorrisonmendez said it’s more of a Nginx server issue. Post Nginx.conf, it will be easier to detect the problem
– Guilherme Nascimento
I believe it’s in Nginx, because the parameter
max_execution_time
affects only the execution of the script, not counting the time spent outside the script (calls to the bank, etc.). At least that’s what the documentation says... http://php.net/manualen/function.set-time-limit.php– Vinícius Gobbo A. de Oliveira