Yeah. I don't see any way to make it read stuff from only disk. I think the normal use case is to have consumers constantly draining the job queues.
-- Chad Kouse On Friday, August 24, 2012 at 1:09 PM, David Leimbach wrote: > I don't need it to be in RAM if it's on disk, and RAM is precious on these > nodes. > > It doesn't appear to be the correct resource utilization for my purposes. > > On Friday, August 24, 2012 10:03:37 AM UTC-7, chadkouse wrote: > > Is there a specific reason you don't want it to put stuff in RAM? > > > > -- > > Chad Kouse > > > > > > On Friday, August 24, 2012 at 1:02 PM, David Leimbach wrote: > > > > > Thanks, however, I was hoping that with "-b" that beanstalk would not > > > still keep all the on-disk contents in RAM. > > > > > > Even with durability on, writing 100,000 512 byte jobs to beanstalk is > > > consuming 109MB of RAM. I was laboring under what appears to be a bad > > > assumption that beanstalk would not keep every job in RAM when I'm using > > > durable queues. > > > > > > Dave > > > > > > On Friday, August 24, 2012 9:10:41 AM UTC-7, chadkouse wrote: > > > > Use the -b flag when starting beanstalkd. > > > > Example: > > > > beanstalkd -b /var/spool/beanstalkd > > > > > > > > -- > > > > Chad Kouse > > > > > > > > > > > > On Friday, August 24, 2012 at 12:04 PM, David Leimbach wrote: > > > > > > > > > ... and is there a way to prevent it from doing so? > > > > > > > > > > I'm thinking about trying to use beanstalk in a situation where I'd > > > > > like actually queue up some "event traffic" for eventual delivery to > > > > > another system. > > > > > > > > > > After inserting 100,000 512 byte records, I'm seeing the resident > > > > > memory size of beanstalkd go up to about 105MB on a 64bit platform. > > > > > > > > > > I've got durable logging on so I can kill and restart the server and > > > > > it quickly gets back up to about 105MB fairly fast. > > > > > > > > > > I'm actually more interested in the durability aspect of events > > > > > rather than speed of retrieval and delivery. I really want a > > > > > persistent queue I guess. > > > > > > > > > > Dave > > > > > > > > > > -- > > > > > You received this message because you are subscribed to the Google > > > > > Groups "beanstalk-talk" group. > > > > > To view this discussion on the web visit > > > > > https://groups.google.com/d/msg/beanstalk-talk/-/OmR4IHGk1SkJ. > > > > > 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 view this discussion on the web visit > > > https://groups.google.com/d/msg/beanstalk-talk/-/hlm0E1aXPLAJ. > > > To post to this group, send email to [email protected] > > > (javascript:). > > > To unsubscribe from this group, send email to > > > [email protected] (javascript:). > > > 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 view this discussion on the web visit > https://groups.google.com/d/msg/beanstalk-talk/-/VIHnIHbbK68J. > 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.
