#################### peak mam usage without -d option (foreground mode) ######################## ------------------------------------------------------------------------------------------------ cat /proc/$PROCESSID/status Name: beanstalkd State: R (running) Tgid: 27467 Pid: 27467 PPid: 27430 TracerPid: 0 Uid: 0 0 0 0 Gid: 0 0 0 0 FDSize: 256 Groups: 0 VmPeak: 1861844 kB VmSize: 1833428 kB VmLck: 0 kB VmHWM: 1813420 kB VmRSS: 1787104 kB VmData: 1819000 kB VmStk: 84 kB VmExe: 48 kB VmLib: 1948 kB VmPTE: 3556 kB Threads: 1 SigQ: 0/16382 SigPnd: 0000000000000000 ShdPnd: 0000000000000000 SigBlk: 0000000000000000 SigIgn: 0000000000001001 SigCgt: 0000000180004202 CapInh: 0000000000000000 CapPrm: ffffffffffffffff CapEff: ffffffffffffffff CapBnd: ffffffffffffffff Cpus_allowed: f Cpus_allowed_list: 0-3 Mems_allowed: 00000000,00000001 Mems_allowed_list: 0 voluntary_ctxt_switches: 64561 nonvoluntary_ctxt_switches: 13
################################ peak mam usage with -d option ################################# ################################ return OUT OF MEMORY HERE ################################# ------------------------------------------------------------------------------------------------ cat /proc/$PROCESSID/status Name: beanstalkd State: S (sleeping) Tgid: 27450 Pid: 27450 PPid: 1 TracerPid: 0 Uid: 0 0 0 0 Gid: 0 0 0 0 FDSize: 64 Groups: 0 VmPeak: 26756 kB VmSize: 26756 kB VmLck: 0 kB VmHWM: 11108 kB VmRSS: 11108 kB VmData: 12328 kB VmStk: 84 kB VmExe: 48 kB VmLib: 1948 kB VmPTE: 76 kB Threads: 1 SigQ: 0/16382 SigPnd: 0000000000000000 ShdPnd: 0000000000000000 SigBlk: 0000000000000000 SigIgn: 0000000000001000 SigCgt: 0000000180004202 CapInh: 0000000000000000 CapPrm: ffffffffffffffff CapEff: ffffffffffffffff CapBnd: ffffffffffffffff Cpus_allowed: f Cpus_allowed_list: 0-3 Mems_allowed: 00000000,00000001 Mems_allowed_list: 0 voluntary_ctxt_switches: 51607 nonvoluntary_ctxt_switches: 0 ------------------------------------------------------------------------------------------------ On Jan 22, 5:43 pm, Anu <[email protected]> wrote: > Please discard previous message and use this message instread > ------ > > I'm testing beanstalkd in two modes > > 1. # Foreground Mode > ./beanstalkd -b binlog > > 2. # Detached Mode > ./beanstalkd -d -b binlog > > For #2., 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 #1. 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.
