Guys,
Since we discovered Beastalkd we're using it more and more in our app
(v1.3).

We have it running since a few days (uptime: 1114539) and I just found
out that it's using a lot of memory even if the queue is almost empty:

 8376 beanstalkd      20   0 1813m 1.7g  388 S    0 44.1  18:19.30
beanstalkd

any hints?

this is the output of stats:

stats
OK 880
---
current-jobs-urgent: 0
current-jobs-ready: 2917
current-jobs-reserved: 143
current-jobs-delayed: 0
current-jobs-buried: 8803
cmd-put: 4722261
cmd-peek: 0
cmd-peek-ready: 1
cmd-peek-delayed: 1
cmd-peek-buried: 5968
cmd-reserve: 2970939
cmd-reserve-with-timeout: 1921777
cmd-delete: 4710412
cmd-release: 0
cmd-use: 28500
cmd-watch: 28497
cmd-ignore: 28493
cmd-bury: 14767
cmd-kick: 0
cmd-touch: 0
cmd-stats: 9
cmd-stats-job: 18572
cmd-stats-tube: 8521
cmd-list-tubes: 2330
cmd-list-tube-used: 0
cmd-list-tubes-watched: 30817
job-timeouts: 131130
total-jobs: 4722261
max-job-size: 10000000
current-tubes: 7
current-connections: 77
current-producers: 18
current-workers: 16
current-waiting: 4
total-connections: 30839
pid: 8376
version: 1.3
rusage-utime: 216.653540
rusage-stime: 287.129944
uptime: 1114539
binlog-oldest-index: 0
binlog-current-index: 0
binlog-max-size: 10485760


thanks in advance!
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to