Aaron and I implemented and deployed to both prod and dev SDS instances a Background Job processing service. We are using a Ruby gem called bj.
For details: http://codeforpeople.com/lib/ruby/bj/bj-1.0.1/README It was very simple to add in. Now the more involved processing that happens to learner session Bundles when they are uploaded is scheduled in a job queue and executed in a sequence of separate processes. Currently a new process is created and destroyed for each task in the job queue. While this is not very efficient it is very safe with respect to the issue of a process that might grow too large due to memory leaks. FYI: SDS changesets 363, 364 http://trac.cosmos.concord.org/sds/changeset/363/trunk We'll be watching to see how long it takes the job queue to catch up when a pulse of bundle uploads arrives at he end of a class. -- - Stephen Bannasch Concord Consortium, http://www.concord.org --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "SAIL-Dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/SAIL-Dev?hl=en -~----------~----~----~----~------~----~------~--~---
