... 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.
