Last modified: 2013-04-22 16:17:01 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T43208, the corresponding Phabricator task for complete and up-to-date bug report information.
First Last Prev Next    This bug is not in your last search results.
Bug 41208 - Maximum execution time exceeded: Levenshtein too slow we guess...
Maximum execution time exceeded: Levenshtein too slow we guess...
Status: RESOLVED FIXED
Product: MediaWiki extensions
Classification: Unclassified
Translate (Other open bugs)
master
All All
: Normal normal (vote)
: ---
Assigned To: Niklas Laxström
https://translatewiki.net/w/i.php?tit...
: performance
Depends on:
Blocks:
  Show dependency tree / graph
 
Reported: 2012-10-19 08:05 UTC by Siebrand Mazeland
Modified: 2013-04-22 16:17 UTC (History)
7 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Siebrand Mazeland 2012-10-19 08:05:48 UTC 
Page editing[1] is not possible because PHP Fatal error:  Maximum execution time of 25 seconds exceeded in /www/translatewiki.net/w/extensions/Translate/ttmserver/TTMServer.php on line 100

Observing CPU at 100% for one core on translatewiki.net during the 25 seconds.
Comment 1 Sumana Harihareswara 2012-10-19 20:51:13 UTC 
Noting that, at first glance, RobLa does *not* think this blocks the Monday deployment of 1.21wmf2 to meta.wikimedia.org.
Comment 2 Andre Klapper 2012-10-19 20:58:29 UTC 
As I cannot edit https://translatewiki.net/w/i.php?title=MediaWiki:Editinginterface/nl&action=edit as an average user and as I'm not familiar with translatewiki.net [yet], the impact is not clear to me.

Does this "only" create problems for editing "surrounding" wikipages, or does this also happen for the *translation* process itself?
Comment 3 Siebrand Mazeland 2012-10-19 21:09:34 UTC 
(In reply to comment #1)
> Noting that, at first glance, RobLa does *not* think this blocks the Monday
> deployment of 1.21wmf2 to meta.wikimedia.org.

I would agree with that assessment.
Comment 4 Sumana Harihareswara 2012-11-13 23:41:20 UTC 
I've checked and I believe this is now nonreproducible.
Comment 5 Niklas Laxström 2012-11-14 07:29:17 UTC 
We currently have time limit at 30 seconds:
<!-- Served in 30.483 secs. -->

This is too slow, so reopening the bug.
Comment 6 Nemo 2012-11-18 19:40:03 UTC 
UserBase just disabled TM for this. :-(

http://userbase.kde.org/Thread:Talk:Translation_Workflow/Translation_memory
Comment 7 Niklas Laxström 2012-11-21 07:34:16 UTC 
https://gerrit.wikimedia.org/r/#/c/34342/
Comment 8 Andre Klapper 2012-11-26 17:59:15 UTC 
Patch has been merged, is a backport planned?
Comment 9 Niklas Laxström 2012-11-26 18:14:34 UTC 
Backport to what? 1.21wmf5 has just been branched and it will be deployed to all relevant WMF projects by Wed.
Comment 10 Andre Klapper 2012-11-26 18:41:03 UTC 
In that case: Can this be closed as RESOLVED FIXED? Or is the patch just considered a "workaround"?
Comment 11 Niklas Laxström 2012-11-26 20:58:14 UTC 
It's not a long term fix, it just fights symptoms. Depending on mood you might want to open a new bug for long term solution or just keep this open ;)
Comment 12 Niklas Laxström 2013-03-27 12:27:37 UTC 
Given that Solr implementation of ttmserver has changed a lot I have my own moods now. It's still not optimal but the original problem has been fixed.
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.

Navigation
Links