Very very nice. Once this is stable we definitely need to blog about this (and give thanks to the Disruptor team too).
Paul On 25 July 2013 15:44, Malinga Purnasiri <[email protected]> wrote: > Hi Srinath, > > This will be greatly improve further more after we implement Disrupter pattern > to the delivery path, hopefully. > And interesting point is; there is no more OOM happening (previously we > suffered lot with this). > > And just one part i want to highlight is that; we have some issue with the > Admin Console after the Disrupter implementation; which we will address > once we have time. Wont be a big issue. > > > On Thu, Jul 25, 2013 at 8:00 PM, Sanjiva Weerawarana <[email protected]>wrote: > >> Wow :-). >> >> >> On Thu, Jul 25, 2013 at 5:56 PM, Srinath Perera <[email protected]> wrote: >> >>> Hi All, >>> >>> We have been working on MB2 performance improvements, based on Disrupter >>> and then batching Cassandra calls and removing some non-critical cassandra >>> calls (e.g. message counters). >>> >>> Following are some initial results >>> >>> 1) With one MB Node, With cached senders, I got about 13K TPS in new >>> perf machines publishing and about 2500 TPS at the receiving side. >>> >>> 2) With one MB Node, With new senders per message (this make sure >>> message is written to the disk), about 2500 TPS at publisher and 2500 TPS >>> at receiver side. (Earlier we got about 1500 TPS before changes ). >>> >>> In the released version, if we send about a Million message very fast .. >>> memory get accumulated and system goes OOM. With disrupter changes this >>> limit is gone. We tested with 3M messages back to back without any trouble. >>> >>> Receiving side bottleneck is caused by Ack sent per message. AQMP >>> support batched Acks, but need to work on that. >>> >>> We have not tested multiple broker scenarios, but the bottleneck is not >>> Cassandra any more. So we think it should scale well. >>> >>> However, these changes need to be carefully reviewed to make sure it >>> does not break anything major. If all is well, we can do a point release >>> with performance improvements. >>> >>> --Srinath >>> >>> >>> >>> >>> >>> -- >>> ============================ >>> Srinath Perera, Ph.D. >>> Director, Research, WSO2 Inc. >>> Visiting Faculty, University of Moratuwa >>> Member, Apache Software Foundation >>> Research Scientist, Lanka Software Foundation >>> Blog: http://srinathsview.blogspot.com/ >>> Photos: http://www.flickr.com/photos/hemapani/ >>> Phone: 0772360902 >>> >>> _______________________________________________ >>> Architecture mailing list >>> [email protected] >>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>> >>> >> >> >> -- >> Sanjiva Weerawarana, Ph.D. >> Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/ >> email: [email protected]; phone: +94 11 763 9614; cell: +94 77 787 6880 | +1 >> 650 265 8311 >> blog: http://sanjiva.weerawarana.org/ >> >> Lean . Enterprise . Middleware >> >> _______________________________________________ >> Architecture mailing list >> [email protected] >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> > > > -- > Malinga Pathmal, > Technical Lead, WSO2, Inc. : http://wso2.com/ > Phone : (+94) 715335898 > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- Paul Fremantle CTO and Co-Founder, WSO2 OASIS WS-RX TC Co-chair, Apache Member UK: +44 207 096 0336 US: +1 646 595 7614 blog: http://pzf.fremantle.org twitter.com/pzfreo [email protected] wso2.com Lean Enterprise Middleware Disclaimer: This communication may contain privileged or other confidential information and is intended exclusively for the addressee/s. If you are not the intended recipient/s, or believe that you may have received this communication in error, please reply to the sender indicating that fact and delete the copy you received and in addition, you should not print, copy, retransmit, disseminate, or otherwise use the information contained in this communication. Internet communications cannot be guaranteed to be timely, secure, error or virus-free. The sender does not accept liability for any errors or omissions.
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
