It actually depends on payload and complexity of queries. If your server keeps hanging and resources are depleted when exposed to production traffic then you need to scale. If you refer[1] you will get an idea about numbers. See under storm scaling sheet. But to date we don't have any production customers on Storm.
[1] https://docs.google.com/a/wso2.com/spreadsheets/d/1TEjXPPClSqKg6n3EVq65U1w8Cpj0RrHRMX5CRUstZRY/edit?usp=sharing Tishan On Fri, Apr 29, 2016 at 2:10 PM, Dulitha Wijewantha <duli...@wso2.com> wrote: > > > On Fri, Apr 29, 2016 at 11:12 AM, Tishan Dahanayakage <tis...@wso2.com> > wrote: > >> Hi Chan, >> >> Please find inline. >> >> On Fri, Apr 29, 2016 at 9:56 AM, Dulitha Wijewantha <duli...@wso2.com> >> wrote: >> >>> Hi guys, >>> I read the article [1] that details a performance test conducted on CEP >>> integration on Storm. I have some questions regarding how this integration >>> actually work and how this fits in with the DAS picture. >>> >>> 1) In the article it says that siddhi runs inside storm. Does this mean >>> that we have converted siddhi engine to a bolt to run inside the storm >>> environment? >>> >> >> Yes you are correct. Siddhi Bolt will be uploaded to storm with all >> dependencies. >> >> >>> 2) How is the CEP query broken down into bolts and spouts? In the >>> documentation its states we have a bunch of annotations to set bolts and >>> spouts for the plan. For example:- do we need to change the way we do a >>> window count? Like create streams separately for the spouts or is this >>> handled by CEP manager? >>> >> >> It is on bolt per query. But if the query is stateless you can have >> multiple bolts per query. If you do not mention theses counts it will start >> with default counts. Also this does not change the way you write siddhi >> queries. >> >> >>> 3) What's the exact difference of Siddhi and Storm? I feel like both >>> have the same concepts. >>> >> >> While Storm is more like a stream processing framework Siddhi is a more >> of a processing library engine. In Storm you need to write your own bolt. >> But in CEP we use a Siddhi bolt and allows you to write your business logic >> in Siddhi. >> >> >>> 4) In a DAS Deployment - does this mean that the event receiver node is >>> going to communicate with storm for processing? Will this incur a >>> significant performance hit on the event receiver? >>> >> >> In the deployment event receiver node will only send to Storm cluster. >> It will not do any processing. It will function more like gateway. While >> actual load on that server will be high I dont think it will be much of a >> problem given that it is just pass through traffic. >> >> On side note you will only need Storm deployment if your event rate is >> too high that HA setup can handle. Normally HA setup can handle a pretty >> high throughput on most scenarios on moderate hardware. >> > > Do we have performance tests that gives us this sweet spot (event rate > number)? > > > >> >> Thanks >> Tishan >> >>> >>> [1] - >>> http://wso2.com/library/articles/2015/12/article-distributed-scaling-of-wso2-complex-event-processor/ >>> >>> Cheers! >>> >>> -- >>> Dulitha Wijewantha (Chan) >>> Software Engineer - Mobile Development >>> WSO2 Inc >>> Lean.Enterprise.Middleware >>> * ~Email duli...@wso2.com <duli...@wso2mobile.com>* >>> * ~Mobile +94712112165 <%2B94712112165>* >>> * ~Website dulitha.me <http://dulitha.me>* >>> * ~Twitter @dulitharw <https://twitter.com/dulitharw>* >>> *~Github @dulichan <https://github.com/dulichan>* >>> *~SO @chan <http://stackoverflow.com/users/813471/chan>* >>> >>> _______________________________________________ >>> Dev mailing list >>> Dev@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> Tishan Dahanayakage >> Software Engineer >> WSO2, Inc. >> Mobile:+94 716481328 >> >> 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, re-transmit, 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. >> > > > > -- > Dulitha Wijewantha (Chan) > Software Engineer - Mobile Development > WSO2 Inc > Lean.Enterprise.Middleware > * ~Email duli...@wso2.com <duli...@wso2mobile.com>* > * ~Mobile +94712112165 <%2B94712112165>* > * ~Website dulitha.me <http://dulitha.me>* > * ~Twitter @dulitharw <https://twitter.com/dulitharw>* > *~Github @dulichan <https://github.com/dulichan>* > *~SO @chan <http://stackoverflow.com/users/813471/chan>* > -- Tishan Dahanayakage Software Engineer WSO2, Inc. Mobile:+94 716481328 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, re-transmit, 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.
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
