2011.02.11 20:59, leif rašė:
For the last few days I have discovered that Pootle is either very slow
or not available at all.
Please ;-)
That's not so easy to debug... :) The last time André did some checks
but could not find anything suspicious.
From a quick glaze at `top`, I would guess we were facing a simple
bottleneck problem, because none of the processes were eating up too
much CPU or RAM.
I suspect slightly that the reason MAY be search bots that were crawling
Pootle, so I've just added a static robots.txt file (previously, it was
being generated dynamically with explicit restriction on almost all
"directories", but I've simply added a "Disallow: /" line instead of all
these restrictions. We'll see whether or not it will help.
Also, it could be that we're reaching a maximum amount of Apache servers
allowed to start (search bots contribute to that too, of course).
A few more ideas for the future:
* redirect all non-ssl requests, not just when the user tries to log in.
* get rid of Apache and install Nginx or Cherokee or something similar
instead
(IMO, the two ideas above are good in either case)
* debug further? :)
Rimas
--
Unsubscribe instructions: E-mail to [email protected]
List archive: http://listarchives.libreoffice.org/www/l10n/
*** All posts to this list are publicly archived for eternity ***
