https://bugzilla.wikimedia.org/show_bug.cgi?id=31197
--- Comment #18 from Nemo_bis <[email protected]> 2011-10-05 20:09:21 UTC --- It's been explained why the feature is expensive, but not why it should be disabled, which is the point of the discussion. There should be some criteria to disable features, otherwise they're disabled randomly. If there are server load problems, was this feature compared to other expensive features to evaluate cost vs. benefit and choose what to disable? Or does "queries taking more than a second are already considered slow" mean that all features which are able to generate queries longer than a second (or any other threshold) will be disabled? If there are not server load problems, why should the feature be disabled? Even if there are problems, can't they be resolved through other means and shouldn't their cost be compared to the benefit of the feature? Last but not least, did someone prove that disabling the feature will actually reduce server load? Users need this (finding edits in specific namespaces), therefore if you don't allow this feature they'll just load the complete list of edits, 5000 at a time, and search the namespace within the pages. In your example: Rambot, 140 000 edits, 28 pages; for the first I got "Served by mw30 in 14.588 secs", this makes a total of almost 7 minutes. That's not the length of the queries and I don't know if it's important, but perhaps it should be checked. -- Configure bugmail: https://bugzilla.wikimedia.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. You are on the CC list for the bug. _______________________________________________ Wikibugs-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
