+++ This bug was initially created as a clone of Bug #630884 +++ 2) performance satellite sync ended at: Import complete: Begin time: Fri Oct 15 05:42:59 2010 End time: Fri Oct 15 07:13:48 2010 Elapsed: 1 hours, 30 minutes, 48 seconds First email was sent at: 7:32 (which is ok) and last was sent at 8:34. This open question how this will behave, if you have to sent errata notification for 1000 systems/users. --- Additional comment from tlestach on 2010-10-19 10:20:14 EDT --- Step to reproduce: 1) sync 5.0 channel with --no-errata 2) register rhel 5.0 to this channel 3) sync all errata 4) wait for emails "Errata Alert" to arive Actual results: aprox. 10 emails per 30 minutes Expected results: all emails should arrive within one or two minute.
spacewalk.git: fda4e5b21b0107ba11d4cb25cf0cabc3e6db1120 For QA: Please test very carefully, if all expected errata notifications will be sent.
bug 720533 & bug 701457 both replace rhnServerNeededView with a custom SQL for results. That may be a better solution here vs using the rhnServerNeededCache. Since all loosely associated (taskomatic performance) - moving over for Errata.
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: Consequence: After syncing of new errata, e-mail notifications get processed very slow and it takes a long time until the notifications get sent. Result: The performance of e-mail notifications processing was significantly improved.
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2011-1162.html