Last modified: 2010-05-15 15:48:19 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 9066 - Perfromance issues potentially caused by locks and timeouts
Perfromance issues potentially caused by locks and timeouts
Status: RESOLVED WORKSFORME
Product: MediaWiki
Classification: Unclassified
Database (Other open bugs)
1.9.x
All All
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
http://train.spottingworld.com
:
Depends on:
Blocks: postgres
  Show dependency treegraph
 
Reported: 2007-02-22 08:59 UTC by Tim Trent
Modified: 2010-05-15 15:48 UTC (History)
1 user (show)

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


Attachments

Description Tim Trent 2007-02-22 08:59:03 UTC
We run PostgreSQL 8.1

Apparently at random the system appears to hang while waiting for an event that
never happens.  In general the server is idle at this point, though random
activity takes places.

To cause the hangs/pseudo-hangs we will do one of the following:

Run a search and attempt to edit.  Result:  Either or both of the search takes
for ever to reach EOJ or an edit may open fast but take up to 60 seconds to submit

Edit several pages simultaneously (tabbed browser) and submit edits as near
simultaneously as posisble.  Result: Edits Do submit, but take of the order of
60 seconds

Server is very lightly loaded indeed (we are in the startup phase)
Comment 1 Greg Sabino Mullane 2007-03-17 20:11:30 UTC
Could not duplicate. Can you try and figure out what is locking or taking so
long? Use the Postgres server logs, and/or check the output of:
select pid, relation:regclass, locktype, granted from pg_locks;
select * from pg_stat_activity;

Also, how many pages do you have, and how long does a search usually take?
Comment 2 Greg Sabino Mullane 2007-04-24 13:51:02 UTC
Changing to "worksforme". If the submitter has more information, please reopen
the bug.

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


Navigation
Links