Return-Path: Delivered-To: apmail-activemq-dev-archive@www.apache.org Received: (qmail 13689 invoked from network); 10 Jun 2007 16:04:54 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 10 Jun 2007 16:04:54 -0000 Received: (qmail 85352 invoked by uid 500); 10 Jun 2007 16:04:57 -0000 Delivered-To: apmail-activemq-dev-archive@activemq.apache.org Received: (qmail 85326 invoked by uid 500); 10 Jun 2007 16:04:57 -0000 Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@activemq.apache.org Delivered-To: mailing list dev@activemq.apache.org Received: (qmail 85317 invoked by uid 99); 10 Jun 2007 16:04:57 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 10 Jun 2007 09:04:57 -0700 X-ASF-Spam-Status: No, hits=-100.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 10 Jun 2007 09:04:53 -0700 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 182177141F8 for ; Sun, 10 Jun 2007 09:04:33 -0700 (PDT) Message-ID: <4423988.1181491473089.JavaMail.jira@brutus> Date: Sun, 10 Jun 2007 09:04:33 -0700 (PDT) From: "Timothy Bish (JIRA)" To: dev@activemq.apache.org Subject: [jira] Commented: (AMQCPP-93) Performance analysis In-Reply-To: <20942071.1174226494454.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/activemq/browse/AMQCPP-93?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39250 ] Timothy Bish commented on AMQCPP-93: ------------------------------------ If you look at the code for these two classes though, there really isn't much there, I've gone through it and made a couple small tweaks that might help, but not very much though. I figured that these would show up as heavy hitters, but since they are really at the heart of the library its not surprising. They are called a lot. If you look through and see any tweaks, to those we can add them, I'd look at the next level up though as the code above those layers is where I bet a lot more of the inefficiencies are going to be. I know for sure where some of the Openwire slowness is coming from but haven't had time to play with it, requires changing the scripts and connector code. Not to brag :) , but our stomp implementation is really sweet there isn't much at all that has to happen to get a message out on the wire as its stored pretty much in wire format in the base frame class always. There's a whole lot more that has to happen when an Openwire message goes out, that code is definitely still young and will need to lot of fine tuning. > Performance analysis > -------------------- > > Key: AMQCPP-93 > URL: https://issues.apache.org/activemq/browse/AMQCPP-93 > Project: ActiveMQ C++ Client > Issue Type: Task > Affects Versions: 2.0 > Reporter: Nathan Mittler > Assignee: Nathan Mittler > Fix For: 2.2 > > > Do a performance analysis on openwire vs stomp. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.