On Thu, Nov 26, 2015 at 4:32 PM, Andrew <catalystgr...@unitedgames.co.uk> wrote: > ....I just want to know why the whole FastCGI Plack loaded Catalyst app came > down half way through, > and how I can have a Perl script process sending 3000 emails without that > happening every time, =S. >
As pointed out already the main problem here is that you are trying to do stuff (sending email) within the app thread, that is you are breaking the app design and should use a batch/background thread to do intensive work (even reading all the emails from database could be a problem, depending on how you do the query and how optimized is the database). I would pick up at least an email alias, that can be easibly auto-generated and updated each time a new user joins. This way you are at least hiding the 3000+ receivers behind a single email, letting the email software to do the stuff it has been built for. The next step would be to use a mailing list, internal or external. The only reason I could see for looping thru every email address could be to store in the database the result of the sending process, which is in my opinion worthless. Luca _______________________________________________ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/