Hi all, I wanted to know how the persistency in beanstalk works.
Does it always put the job in both RAM and disk and just uses the disk as a persistent storage or does it also feature a flow-to-disk scenario in which when RAM fills up it will always write new jobs to the disk and when all jobs in RAM are done, it will read a chunk from the disk to continue the work. The first logic I described (everything is in both RAM and disk for persistency) is the way RabbitMQ works (at least currently up to the latest release - 1.7). One of the most requested features is a flow-to-disk feature similar to Twitter's (rather new) Kestrel (the jobs queue that replaced Sterling/Scarling). Thanks, Eran --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
