On Nov 27, 6:28 pm, "Graham Barr" <[EMAIL PROTECTED]> wrote:
> yeah, it seems like you are putting them in and taking them out. > > you also seem to be calling stats-job. Is that the worker or the producer > doing that ? > > what is your average/max job size ? > > do you have binlog turned on ? I just ran into this problem with binlog turned on. leaks says: Process 162: 39 nodes malloced for 1574500 KB Process 162: 0 leaks for 0 total leaked bytes. stats says: current-jobs-urgent: 0 current-jobs-ready: 0 current-jobs-reserved: 0 current-jobs-delayed: 0 current-jobs-buried: 0 cmd-put: 31 cmd-peek: 0 cmd-peek-ready: 0 cmd-peek-delayed: 0 cmd-peek-buried: 0 cmd-reserve: 61 cmd-reserve-with-timeout: 0 cmd-delete: 31 cmd-release: 0 cmd-use: 31 cmd-watch: 30 cmd-ignore: 30 cmd-bury: 0 cmd-kick: 0 cmd-touch: 0 cmd-stats: 1 cmd-stats-job: 0 cmd-stats-tube: 0 cmd-list-tubes: 0 cmd-list-tube-used: 0 cmd-list-tubes-watched: 31 job-timeouts: 0 total-jobs: 31 max-job-size: 65535 current-tubes: 1 current-connections: 1 current-producers: 0 current-workers: 0 current-waiting: 0 total-connections: 65 pid: 162 version: v1.1-45-gb637898 rusage-utime: 0.848163 rusage-stime: 0.808622 uptime: 389618 killing 162 made my machine much happier. :) --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
