Hi Mike, I think you are using Cassandra comes embedded with MB and not running a different MB. Please confirm.
How many topics do you use? Also, could you send us your clients for producer and consuming? We will check this, and in general it is high. However, we do poll Cassandra to get the messages (and we sleep a bit if there is no message) before delivering. But if 55TPS just enough to return at least one more message at each poll, then it could take some CPU. --Srinath On Fri, Sep 6, 2013 at 10:48 AM, Mike Stoddart <[email protected]> wrote: > I added support for publishing objects to the Message Broker using JMS to > my application. The test scenario includes two clients that connect, one > producing and one consuming. I'm using the sample code for working with > topics and I'm sending ObjectMessage instances. The statistics seem to be: > > rate: 55 messages/second > serialized object size: approx 1k > > The Message Broker is running at 30% on my MacBook Pro with 16Gb. > > This seems awfully high - are my expectations way off? > > Thanks > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- ============================ Srinath Perera, Ph.D. http://people.apache.org/~hemapani/ http://srinathsview.blogspot.com/
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
