Infrastructure

Well. it's fast and fine now... but yesterday it didn't work
I just paste a/some words in the search field and hit enter, that's all

There's not much to do about that - pootle is just very slow for some operations. Initial start takes long, so does creating files for download and similar. So when you're the poor guy triggering the creation of a search-index, or are the first to create the files for offline-translation, then there is some waiting time.

So I wonder what you mean with "regularily" - can you be more precise with that? It might be possible to run cronjobs to simulate what you're doing, so that when a visitor requests the site it won't be as slow, but of course might have adverse effects ("blocking" pootle for stuff that nobody uses)..

I will try to keep some statistics next weeks or so.
Roughly: last 2 week, I was there say each 2nd day and half of the time it was really slow or unresponsive.
All with the same actions: ctrl+shft+s <foo> enter
thanks,
Cor

Talked to Cloph, some actions in Pootle simply are slow. If you can send some details, he can check if it's a bug or if it's Pootle issue - depending on that, we can close the issue or leave it open. Waiting for your feedback then. :)

Florian Effenberger wrote:

some actions in Pootle simply are slow.

See my previous explanation. The same actions are sometimes terribly slow and then another time fine.
You may close - if/when I have collected data, I can reopen :)
Ciao

This needs to reopened.
Details:
Suck again regularly
See posts on mailinglist.

Will be discussed in Monday's team call, first feedback from Cloph:

• we need Newrelic access (my credentials don't work anymore, poked Dwayne for help)
• moving Pootle to our infra and giving it more than the current 8 GB of RAM
• SSD would help, but nothing we can provide from our infra platform
• put Pootle's database into RAM on our platform
• split the translations for the different LO versions into separate pootle installations
• some better use of table-indices might also give a performance boost

Sounds OK. Thanks!

just to not misinterpret it as a list of planned things, esp. the split into individual projects would cause account-maintenance annoyance, so at least that item is last-resort only. Hopefully the reporting gives hints on what can be done besides more RAM...

Sophie and I try to meet Dwayne at FOSDEM, and see how we can take it from there - before rushing another server migration, I'd like to talk to him first to see what they can do for us

Sophie just reached out to Dwayne again
If all else fails, Pootle needs to be migrated to our own infra
Cloph estimates this takes about one day of work, plus more downtime when copying/migrating over the DB, so the FOSDEM approach is the preferred one atm, also because of #1005