On Tue, Oct 6, 2009 at 10:25 PM, Dustin <[email protected]> wrote: > I saw a mention of beanstalkd and a kind of temporal overflow thing > to keep memory down. Might be a neat idea to bring into the main > server: > > http://www.slideshare.net/igrigorik/ruby-c10k-high-performance-networking-rubykaigi-09
That is cool. It seems feasible to keep the job body (and maybe a good chunk of the ~93 bytes of overhead) on disk with just a stub in memory for each delayed job. An aggressive implementation could probably get it down to just a couple of words per stub. But I think to put the *entire* job on disk would require turning beanstalkd into a database inside. kr --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
