Return-Path: Delivered-To: apmail-activemq-users-archive@www.apache.org Received: (qmail 80739 invoked from network); 25 Jul 2007 21:21:55 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 25 Jul 2007 21:21:55 -0000 Received: (qmail 22127 invoked by uid 500); 25 Jul 2007 21:21:56 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 21832 invoked by uid 500); 25 Jul 2007 21:21:55 -0000 Mailing-List: contact users-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@activemq.apache.org Delivered-To: mailing list users@activemq.apache.org Received: (qmail 21822 invoked by uid 99); 25 Jul 2007 21:21:54 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 25 Jul 2007 14:21:54 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of rajdavies@gmail.com designates 66.249.92.171 as permitted sender) Received: from [66.249.92.171] (HELO ug-out-1314.google.com) (66.249.92.171) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 25 Jul 2007 14:21:52 -0700 Received: by ug-out-1314.google.com with SMTP id q2so451768uge for ; Wed, 25 Jul 2007 14:21:31 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:mime-version:in-reply-to:references:content-type:message-id:content-transfer-encoding:from:subject:date:to:x-mailer; b=OxxbLQwamX9NQdj5ICUEcOXIbITWylWkyeQOnCGOZlTXwowHWwsAcOlmCCgLbKl+TBx2cMkbd1V1oUDQbEUYIiXteGu1e951UW41PZBwtWPL4G1L+R9bc+ohrBeszG9LBZ87lZR12Pcc6M17wBE0zXm/lMYyswXxfzRkmBmQzew= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:mime-version:in-reply-to:references:content-type:message-id:content-transfer-encoding:from:subject:date:to:x-mailer; b=owMwf2sBYF63fAwVlsPx8iXXIjTjlJzHKrSK/w1dJ8LQbISUwlXjzydbV+OCbMS/w/GKNMXo66gxBlroYtrf6lK1Y2bYR/jY1/NZ4Di4n8tNXH9IzzUbxp3TO6IAmQWYKFCwqF/yqfhoBpWlQErFxpAfDxuu9x2huiy7RYqhbDw= Received: by 10.86.80.5 with SMTP id d5mr710110fgb.1185398491615; Wed, 25 Jul 2007 14:21:31 -0700 (PDT) Received: from ?192.168.1.75? ( [81.154.167.67]) by mx.google.com with ESMTPS id f3sm1528831nfh.2007.07.25.14.21.30 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 25 Jul 2007 14:21:31 -0700 (PDT) Mime-Version: 1.0 (Apple Message framework v752.3) In-Reply-To: <11800104.post@talk.nabble.com> References: <11800104.post@talk.nabble.com> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <6E776C20-1E48-421B-BD16-10DB04619C42@gmail.com> Content-Transfer-Encoding: 7bit From: Rob Davies Subject: Re: ApacheMQ broker memory consumption and crash Date: Wed, 25 Jul 2007 22:21:27 +0100 To: users@activemq.apache.org X-Mailer: Apple Mail (2.752.3) X-Virus-Checked: Checked by ClamAV on apache.org which version of amq ? The version really makes a difference to the answer ;) On Jul 25, 2007, at 10:14 PM, razaimperial wrote: > > Hi guys, > > Like others, Im doing a stress test on MQ. I dont think I have a > config > issue but just in case. > > I am simulating lots of topic from 14 connections (in a real > deployment each > stream would be a seperate connection), each connection has around > X number > of topic. There is just one consumer subscribed to all of these > topics. The > message size is quite large though, about 25k per packet, sent > every 15 > seconds for each topic. > > The broker does fine until about 100 topics per connection in terms > of CPU > utilization, but the memory footprint is quite large. The utilization > progressively increases (starts at around 5% (of 4GB)) and > increases as more > topics join the system. However it doesnt go past 15.5% > (translating to > around 600mb) and after 15.5 percent first the CPU utlization goes > to 99% > lingers there for a few seconds (the broker is sending messages at > this > point) and the broker just dies. > > I've tried increasing the memory assigned to the broker but Im not > sure if > Im doing it right. First off, there was the same behaviour by > default, even > though the documentation says the default is 20mb RAM use, clearly > not the > case. But even when I change that to 600mb or more, I get the exact > same > behaviour. > > Im editing the default apachemq.xml file that ships with the > installation. > > Help much appreciated > -- > View this message in context: http://www.nabble.com/ApacheMQ-broker- > memory-consumption-and-crash-tf4147994s2354.html#a11800104 > Sent from the ActiveMQ - User mailing list archive at Nabble.com. >