On Wed, Feb 10, 2010 at 5:29 AM, Carl <[email protected]> wrote: > Is there a better to achieve this?
There are some options: You could have producers check the queue size, estimating memory use, before submitting jobs. They can start dropping jobs on the floor if the queue looks too big. You could limit beanstalkd's heap size with the ulimit command. With a restricted heap, beanstalkd will reject jobs, replying OUT_OF_MEMORY, as long as it's at the limit. You could just let it grow. When beanstalkd outgrows your physical memory, the machine will start swapping. Maybe that's okay; it depends on your needs. 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.
