You're absolutely correct. 6 seconds or even db timeouts an just a few
connections mean that something is wrong. It's either much more connections
than it seems or there is a problem in the code or even OS.
Ricardo made a valid observation in regards to rogue bots. This problem is
more wide spread than many people think and these suckers can literally
grind your site to a halt... Check your logs for connections coming from:
208.115.96.0/19
212.113.32.0/21
213.186.96.0/19
217.69.128.0/21
There might be others, these IP ranges are a subset from a research made a
couple of months ago.
On Thursday, April 11, 2013 3:49:22 PM UTC+2, Niphlod wrote:
>
> 6 seconds on a db connection (or query, btw) seems unlikely .... on this
> scale, even if it's true that most of the development platform (read, your
> home pc) are now faster than the various VPS lying around, when you coded
> that particular page you probably noticed a huge loading time in the first
> place.....
>
> if out of the blue the performances are dropping it's usually because of
> deployment issues or "I've been slashdotted" scenarios.
> A concurrency scenario of 5 pages shouldn't lead to a 504 even on the
> poorest platform out there ("raspberrypi scale")
>
>
--
---
You received this message because you are subscribed to the Google Groups
"web2py-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to web2py+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
