Last modified: 2010-05-15 15:48:27 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 T11638, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 9638 - Large Notifications Fail
Large Notifications Fail
Status: RESOLVED FIXED
Product: MediaWiki
Classification: Unclassified
Email (Other open bugs)
1.9.x
PC Windows NT
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2007-04-20 17:33 UTC by Rick Blasingim
Modified: 2010-05-15 15:48 UTC (History)
1 user (show)

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


Attachments

Description Rick Blasingim 2007-04-20 17:33:43 UTC
Some of our articles have 1200+ accounts watching. We've found that 50-100 
notifications are sent before the update is lost and the rest of the 
notifications fail.

The problem is max_execution_time in PHP.ini. Unless we tweak this value, we're 
limited to the number of notifications that can be sent in 30 seconds. For 1200 
notifications, we're guessing we'd have to tweak it to 20 minutes. Most editors 
will assume there's a been a failure if it takes 20 minutes to make an update.

The best solution would seem to be less e-mail. Would it be possible to have 
multiple addresses on the same message? Maybe use the BCC field to hide them? 
Does SMTP have limits on adresses or field size?

Or...would it possible to have the update made BEFORE the notifications are 
sent? I don't know if that would change the editors' experience in terms of 
wait time, but updates wouldn't be lost.
Comment 1 Brion Vibber 2007-04-25 19:44:43 UTC
The notification mails have per-user customizations, including language
preference and the last-seen version used to create diff links, so it's
necessary to do generate them per-user.

There probably are optimizations that can be made, though. Sending multiple
mails over one connections? Batching? Background queue? Dunno exactly.
Comment 2 Rob Church 2007-05-12 00:31:19 UTC
River has introduced the $wgEnotifImpersonal and $wgEnotifUseJobQ options in
trunk to help with large sites.
Comment 3 Antoine "hashar" Musso (WMF) 2007-05-19 20:29:01 UTC
Fixed by r21897 r21898 r21924 r21925 r21961 at least. Those would
be in MediaWiki 1.11.

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


Navigation
Links