Hi,
I've had beanstalkd running in production for over a week now, and
have seen a steady increase in the amount of memory beanstalkd has
been using up. It is currently using 44% of memory (1.7GB ec2 medium
instance) according to top.
The queue itself currently has 20 tubes, each one with no jobs stored
in it. An example of stats_tube for one of these 20 tubes is as
follows:
{'current-jobs-delayed': 0, 'pause': 0, 'name':
'results..defdeinvestmentbankinginstitute', 'cmd-pause-tube': 0,
'current-jobs-buried': 0, 'pause-time-left': 0, 'current-waiting': 0,
'current-jobs-ready': 0, 'total-jobs': 1, 'current-watching': 2,
'current-jobs-reserved': 0, 'current-using': 1, 'current-jobs-urgent':
0}
Does anyone know what might be responsible for eating up this much
memory over time?
Cheers.
--
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.
