I'm testing beanstalkd in two modes 1. # Foreground Mode ./beanstalkd -b binlog
2. # Detached Mode ./beanstalkd -d -b binlog For #1., beanstalkd can only handle hundreds of thousand messages before it return OUT_OF_MEMORY. Each message has size less than 1K and I don't think my system is really running out of memory, checking with free command I still has more than 5G memory free left. but for #2. I can send up to multi-millions messages to the queue without problem. I've 8G memory running on Ubuntu and using beanstalkd-1.4.3 compiled from source. Linux 2.6.31-14-server #48-Ubuntu SMP Fri Oct 16 15:07:34 UTC 2009 x86_64 GNU/Linux "nohup ./beanstalkd -b binlog &" is my current solution but I think is maybe there is a bug in detach mode. # ulimit -a core file size (blocks, -c) 0 data seg size (kbytes, -d) unlimited scheduling priority (-e) 20 file size (blocks, -f) unlimited pending signals (-i) 16382 max locked memory (kbytes, -l) 64 max memory size (kbytes, -m) unlimited open files (-n) 65535 pipe size (512 bytes, -p) 8 POSIX message queues (bytes, -q) 819200 real-time priority (-r) 0 stack size (kbytes, -s) 8192 cpu time (seconds, -t) unlimited max user processes (-u) unlimited virtual memory (kbytes, -v) unlimited file locks (-x) unlimited -- 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.
