Hi Daya, What is the query you used? Could you try this monitoring the size of the queue (should add a log to show size of the queue for every 100k message or so)? Can we test with non-blocking queue?
Another explanation to drop is that there are too much events in the window at 1.5M TPS. But we need to verify. Can we test for longer times ..like 10m, 15m, 1, 3h? When this is done, the next step is Joins. --Srinath On Wed, Nov 13, 2013 at 8:12 AM, Srinath Perera <[email protected]> wrote: > Daya, no private mails pls .. should sent to arch@ .. I will respond there > > > On Tue, Nov 12, 2013 at 6:37 PM, Daya Attapattu <[email protected]> wrote: > >> Here are the throughput I got with varying window sizes. Throughput was >> measured from input stream with a blocking queue. I think the sudden drop >> around 1.5M when queue gets full. So, values before 1.5M are not valid. >> (Not all those events go through CEP, some just accumulate in input >> queue.) But the more important thing is we don't see a substantial >> performance variation. >> >> Regards, >> >> - Daya >> >> -- >> Daya Atapattu, Ph.D. >> Senior Architect, WSO2 Inc. >> Visiting Faculty, University of Moratuwa >> Phone: +94 77 047 4730, +1 203 484 7099 >> >> > > > -- > ============================ > Srinath Perera, Ph.D. > http://people.apache.org/~hemapani/ > http://srinathsview.blogspot.com/ > -- ============================ 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
