[rabbitmq-discuss] beam.smp takes a lot of CPU and memory
Mutaz Qasem
mutazmq at gmail.com
Sat Nov 13 17:10:40 GMT 2010
Hi Matthew
There are few already. a message every hour! Please advise
Thank you
Mutaz
On Sat, Nov 13, 2010 at 4:00 PM, <
rabbitmq-discuss-request at lists.rabbitmq.com> wrote:
> Send rabbitmq-discuss mailing list submissions to
> rabbitmq-discuss at lists.rabbitmq.com
>
> To subscribe or unsubscribe via the World Wide Web, visit
>
> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
> or, via email, send a message with subject or body 'help' to
> rabbitmq-discuss-request at lists.rabbitmq.com
>
> You can reach the person managing the list at
> rabbitmq-discuss-owner at lists.rabbitmq.com
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of rabbitmq-discuss digest..."
>
>
> Today's Topics:
>
> 1. jsonrpc-channel not showing up under localhost:55672
> (???? ?????? / Emil Ivanov)
> 2. Re: jsonrpc-channel not showing up under localhost:55672
> (Simon MacMullen)
> 3. beam.smp takes a lot of CPU adn memory (Mutaz Qasem)
> 4. Re: beam.smp takes a lot of CPU adn memory (Matthew Sackman)
> 5. Re: Passing null for 'arguments' to queueBind() (Michael Bridgen)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Fri, 12 Nov 2010 14:08:55 +0200
> From: ???? ?????? / Emil Ivanov <emil.vladev at gmail.com>
> Subject: [rabbitmq-discuss] jsonrpc-channel not showing up under
> localhost:55672
> To: rabbitmq-discuss at lists.rabbitmq.com
> Message-ID:
> <AANLkTinjd6sxv+NSFoOehZXDFS_Am1rx_ZTBiB+RgFnE at mail.gmail.com<AANLkTinjd6sxv%2BNSFoOehZXDFS_Am1rx_ZTBiB%2BRgFnE at mail.gmail.com>
> >
> Content-Type: text/plain; charset="utf-8"
>
> Good day,
>
> I just installed rabbitmq 2.1.1 via .deb package on Ubuntu 10.10 and
> got the .ez files for the jsonrpc-channel and management plugins. When
> I visit http://localhost:55672/ I see Management Console, HTTP API,
> Command Line Tool entries. However - there is no entry for
> jsonrpc-channel (for the examples). I've managed to get it running
> with rabbitmq 1.7, but no luck with 2.1.1. Attaching the logs.
>
> Regards,
> Emil
>
> --
> My place to share my ideas:
> http://bolddream.com (now live :)
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: rabbit.log
> Type: text/x-log
> Size: 813 bytes
> Desc: not available
> URL: <
> http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20101112/8f19e546/attachment-0001.bin
> >
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: startup_log
> Type: application/octet-stream
> Size: 3232 bytes
> Desc: not available
> URL: <
> http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20101112/8f19e546/attachment-0001.obj
> >
>
> ------------------------------
>
> Message: 2
> Date: Fri, 12 Nov 2010 12:18:46 +0000
> From: Simon MacMullen <simon at rabbitmq.com>
> Subject: Re: [rabbitmq-discuss] jsonrpc-channel not showing up under
> localhost:55672
> To: rabbitmq-discuss at lists.rabbitmq.com
> Message-ID: <4CDD30A6.2050901 at rabbitmq.com>
> Content-Type: text/plain; charset=UTF-8; format=flowed
>
> On 12/11/10 12:08, ???? ?????? / Emil Ivanov wrote:
> > I just installed rabbitmq 2.1.1 via .deb package on Ubuntu 10.10 and
> > got the .ez files for the jsonrpc-channel and management plugins. When
> > I visithttp://localhost:55672/ I see Management Console, HTTP API,
> > Command Line Tool entries. However - there is no entry for
> > jsonrpc-channel (for the examples). I've managed to get it running
> > with rabbitmq 1.7, but no luck with 2.1.1. Attaching the logs.
>
> Hi Emil. The .ez file for jsonrpc-channel does not install the examples,
> since there would be no obvious way to remove them for production use.
> And the rpc and js_root contexts don't appear in the list since there's
> no point directly clicking on them.
>
> Unfortunately this does mean it's not exactly obvious that anything is
> happening! If you go into the management plugin overview page and expand
> "Applications" you should find rabbit_jsonrpc, rabbit_jsonrpc_channel
> and rfc4627_jsonrpc applications running.
>
> I'll have a think about how we can make this clearer.
>
> Cheers, Simon
>
> --
> Simon MacMullen
> Staff Engineer, RabbitMQ
> SpringSource, a division of VMware
>
>
>
> ------------------------------
>
> Message: 3
> Date: Fri, 12 Nov 2010 18:56:28 +0400
> From: Mutaz Qasem <mutazmq at gmail.com>
> Subject: [rabbitmq-discuss] beam.smp takes a lot of CPU adn memory
> To: rabbitmq-discuss at lists.rabbitmq.com
> Message-ID:
> <AANLkTin9_d=PNu6HNet_yGv6yU3z+LnDJR_zZDNsWboj at mail.gmail.com<PNu6HNet_yGv6yU3z%2BLnDJR_zZDNsWboj at mail.gmail.com>
> >
> Content-Type: text/plain; charset="iso-8859-1"
>
> Hi
>
> beam.smp is taking ebtween 70% - 90% of my CPU and around 780M RES and 980
> VIRT.
>
> I'm running rabbitmq-server 1.8.1
> and Erlang R14A (erts-5.8) [source] [64-bit] [smp:2:2] [rq:2]
> [async-threads:0] [hipe] [kernel-poll:false]
>
> Any ideas please?
>
> Thank you in advance
> Mutaz
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
> http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20101112/5745b5c9/attachment-0001.htm
> >
>
> ------------------------------
>
> Message: 4
> Date: Fri, 12 Nov 2010 15:28:00 +0000
> From: Matthew Sackman <matthew at rabbitmq.com>
> Subject: Re: [rabbitmq-discuss] beam.smp takes a lot of CPU adn memory
> To: rabbitmq-discuss at lists.rabbitmq.com
> Message-ID: <20101112152800.GV22102 at rabbitmq.com>
> Content-Type: text/plain; charset=us-ascii
>
> On Fri, Nov 12, 2010 at 06:56:28PM +0400, Mutaz Qasem wrote:
> > beam.smp is taking ebtween 70% - 90% of my CPU and around 780M RES and
> 980
> > VIRT.
> >
> > I'm running rabbitmq-server 1.8.1
> > and Erlang R14A (erts-5.8) [source] [64-bit] [smp:2:2] [rq:2]
> > [async-threads:0] [hipe] [kernel-poll:false]
> >
> > Any ideas please?
>
> Send fewer messages?
>
> Matthew
>
>
> ------------------------------
>
> Message: 5
> Date: Fri, 12 Nov 2010 17:43:38 +0000
> From: Michael Bridgen <mikeb at rabbitmq.com>
> Subject: Re: [rabbitmq-discuss] Passing null for 'arguments' to
> queueBind()
> To: rabbitmq-discuss at lists.rabbitmq.com
> Message-ID: <4CDD7CCA.30509 at rabbitmq.com>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> >> It *is* a problem though when the groups are formed dynamically on
> >> a per message basis, i.e. when each consumer has a unique secret
> >> token, known to the producer, and the producer constructs the
> >> recipient group of the message on the fly by including all the
> >> intended recipient's tokens in the message headers.
> >
> > I understand you now, and above is exactly the situation I have. I
> > wonder if a custom exchange type can remove headers from a message
> > prior to delivery.
>
> Here is a design:
>
> Allow CC and BCC fields* when publishing. These are given to exchange
> types** when routing (i.e., they are part of the envelope); and, the
> routing code removes Bcc before actually delivering to queues.
>
> Full semantics left as an exercise*** for the reader.
>
> * They would probably have to be put in message headers, but possibly
> they could be given specific support in our clients.
>
> ** We'd update direct and topic to take account of them; fanout and
> headers don't need to, and other types given be given the fields and do
> what they like.
>
> *** For example, "" is a valid routing key, so how do you send to
> multiple recipients just with BCC field?
>
>
> Michael
>
>
> ------------------------------
>
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>
>
> End of rabbitmq-discuss Digest, Vol 42, Issue 40
> ************************************************
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20101113/c4123be6/attachment.htm>
More information about the rabbitmq-discuss
mailing list