On Nov 28, 2:28 am, "Graham Barr" <[EMAIL PROTECTED]> wrote: > On Thu, Nov 27, 2008 at 5:15 PM, Andreas Fuchs <[EMAIL PROTECTED]> wrote: > > That's great news! However, I have only one permanent non-default > > tube, just putting jobs into it. (See the stats output above, my > > current-tubes is 2). > > yeah, it seems like you are putting them in and taking them out.
What Async_observer does (plus putting them back), basically. > you also seem to be calling stats-job. Is that the worker or the producer > doing that ? I would never have spotted this. That was async_observer's logging function. Commenting that chunk out from async_observer seems to make the leak go away: After a few of these job things (where it would previously consume hundreds of MB), beanstalkd now consumes only about 444 kBytes, according to ps (-: So it seems like stats-job is leaking somewhere... > what is your average/max job size ? Default setting: Looking at the code, it's ((1 << 16) - 1) (-: > do you have binlog turned on ? Don't know how to do that, so that's at the default setting (guessing off). Thanks so much for diagnosing this! To us, the individual job stats aren't very important, so we'll just comment them out in our copy of the async_observer plugin; it would be good to fix the underlying cause, though. Cheers, Andreas. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
