Timeout error.Launchpad 2.1.8 (r6976)

[Petr E. Antonov]

Timeout error while trying to retrieve: https://translations.edge.launchpad.net/ubuntu/intrepid/+source/gutenprint/+pots/gutenprint/ru/+translate?show=untranslated&start=0&batch=300

More related OOPSes, misplaced in bug 241394: OOPS-982B2121, OOPS-983E1925
Recently: OOPS-991EC177, OOPS-991EB208. To reproduce I just entered the above link, timed out all my tries.

[Petr E. Antonov (antpeter)]

Timeout error

Sorry, something just went wrong in Launchpad.

We’ve recorded what happened, and we’ll fix it as soon as possible. Apologies for the inconvenience.

Trying again in a couple of minutes might work.

(Error ID: OOPS-991ED54)

[Petr E. Antonov (antpeter)]

The same for: https://translations.edge.launchpad.net/ubuntu/intrepid/+source/gutenprint/+pots/gutenprint/ru/+translate?show=untranslated&start=0&batch=200

[Данило Шеган (danilo)]

It'd be nice if this was possible, but the main question here is: Petr, why do you need a batch size of 200?

I cannot imagine it being comfortable to work with a page that long, so I am really looking forward to hearing why would you do it in the first place?

[Petr E. Antonov (antpeter)]

I don't need it in this instance. It's only for testing.

When I make the translation, I use 50-100 for batch (50 for translation, 100 for reviewing). The default batch=10 is very small I think (especially for reviewing) and not comfortable for me. I use such big values because there are a lot of similiar phrases during translation. The editing of similiar phrases on long pages more comfortable for me.

But I need the big value for batch (>300) for the list viewing of programs which I can translate (https://translations.edge.launchpad.net/ubuntu/intrepid/+lang/ru , for example), because sorting is working only for viewing page. I think the sorting must work for ENTIRE list of programs. And the big batch value will not be necessary after that.

[Jeroen T. Vermeulen (jtv)]

Timeouts are something we hate, but there's another side as well: experience has shown that optimizing this page can be a lot of work. Also, there's no guarantee of a radical improvement.

Petr, before we decide what to do with this bug: this page's performance should have improved, at least for some cases, with the fix to bug 259433. That fix was rolled out less than a day ago. Can you check whether it makes a difference for you?

[Ursula Junque (ursinha)]

More oopses happened lately, so marking it as new for it to be triaged again.

[Данило Шеган (danilo)]

These OOPSes on staging were triggered because of dead-locks caused by a message-sharing-populate script Jeroen was testing on staging. These are unrelated to the other ones and are actually a problem in message-sharing-populate script which jtv will work on fixing.

[Jeroen T. Vermeulen (jtv)]

Most of these timeouts have been fixed over time. There are still a few (we have another optimization in the pipeline for the next release, and a good idea of what to try next) but I'm closing this bug to avoid confusion between the old problems (mainly a huge user-selected batch size that's not supported any more) and the few that remain. See bug 531526 for more recent work.