I think a good general architecture for Beanstalk is to store as little information in each job body as possible - in your case, for example, dont store the complete email body but just an ID to a DB record - from which you can generate the email text at job processing time.
/Cody On Tue, Sep 7, 2010 at 3:55 PM, Hoan Ton-That <[email protected]> wrote: > Hey > > I'm wondering how delayed jobs are stored. We are using it for sending > reminder emails. > > What happens if we queue tons of emails 7 days from now? > What about 80 days from now? > When will beanstalkd run out of memory? > Is it a suitable replacement for having cron send mass emails? > > I really like the software, its very easy to use and get running. For > me the delayed jobs are the killer feature. > > Thanks > Hoan > > -- > You received this message because you are subscribed to the Google Groups > "beanstalk-talk" 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/beanstalk-talk?hl=en. > > -- You received this message because you are subscribed to the Google Groups "beanstalk-talk" 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/beanstalk-talk?hl=en.
