Single email per student/template
Description
Environment
Test Plan
Attachments
Activity
Jim Eng January 3, 2011 at 7:54 AM
EVALSYS-764, EVALSYS-766, and are being consolidated to clarify the issues. All work will be done under and the others will be closed as duplicates.
Richard Ellis October 18, 2010 at 7:37 AM
Fixed in 1.2 UM Branch – needs to be merged to trunk
Richard Ellis September 27, 2010 at 11:58 AM
Issue resolved in branch.
Richard Ellis August 19, 2010 at 7:37 AM
The new work described – preparing email for groups distributed across cluster nodes – was tested but found to be slower that the original approach of preparing all email on a single node, so the new work was backed out at U-M.
Sean Michael Demonner August 7, 2009 at 10:10 AM
I think we may have the controls we need on the delivery side, we just need to test them to make sure they're doing what we expect.
Using Dick's example, in order to get 1000 emails sent every ten minutes I would make the following settings in the tool:
Send queued email every: 10 mins
Begin polling for queued notifications after: 1
Number of emails to process before pausing: 1000
Number of seconds to pause before processing more email: 0
Number of sets (lock names) when queuing notifications: 32 (assuming 32000 students with each set consisting of 1000 students)
Does that look correct? If that is correct, the queue would drain in a little over 5 hours, 1000 emails at a time every 10 minutes.
Single Email per Student: a single email is generated for each student, regardless of the number of open evaluations that student has (vs the trunk behavior of sending an email for every open eval to each student).