Last modified: 2013-06-18 16:04:37 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 T19333, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 17333 - simplewiki is slow to respond to the watchlist request
simplewiki is slow to respond to the watchlist request
Status: RESOLVED INVALID
Product: MediaWiki
Classification: Unclassified
Watchlist (Other open bugs)
unspecified
All All
: Low enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
http://simple.wikipedia.org
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-02-03 03:31 UTC by NonvocalScream
Modified: 2013-06-18 16:04 UTC (History)
3 users (show)

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


Attachments

Description NonvocalScream 2009-02-03 03:31:25 UTC
When I pull my watchlist from home or work, the site is very slow to respond compared to other wikis.
Comment 1 Chad H. 2009-02-03 03:32:44 UTC
I don't think this is related to Simple only. I've heard other people complaining about slowness on watchlists.
Comment 2 Siebrand Mazeland 2009-02-04 10:18:42 UTC
Is this a Wikimedia issue, or should it be dealt with as a MediaWiki scalability issue, and should the bug summary be reworded, and the issue product/component be changed?
Comment 3 Chad H. 2009-02-04 12:59:49 UTC
I suppose that depends. If we can fine-tune the watchlist some to get better performance, then it's a MediaWiki issue. If watchlist is about as good as its gonna get, then it's either a Wikimedia issue or INVALID, I suppose.
Comment 4 Siebrand Mazeland 2009-02-04 16:47:42 UTC
Update product/component based on comment 3.
Comment 5 Nemo 2012-07-25 07:42:38 UTC
No way this bug can still be valid/useful after 3+ years.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links