Hi Sajith,
Do you have plot which shows how the TPS varies with the number of events
(for the new results)? I would like to see if there is an improvement
(reduction) in the variation in the TPS.
Also what are the main bottlenecks and performance issues which have been
fixed?
Thanks
On Mon,
We have completed the performance test for IS-Analytics for a Single DAS
node after fixing the bottlenecks and performance issues we found in the
initial testing. Following are the results,
*Case 1 : *Not persisting any data streams only siddhi queries were
running. TPS : 150K.
*Case 2* : Incomi
On Wed, Jun 29, 2016 at 9:23 PM, Dulitha Wijewantha
wrote:
> Hi Mohan/Sajith,
> Can you please explain what this particular scenario was in IS? Is this a
> counting scenario on a window? This would provide input for others who are
> writing real time analytics on CEP.
>
Yes, Here we have mainly
Hi Mohan/Sajith,
Can you please explain what this particular scenario was in IS? Is this a
counting scenario on a window? This would provide input for others who are
writing real time analytics on CEP.
Cheers~
On Mon, Jun 27, 2016 at 5:50 PM, Mohanadarshan Vivekanandalingam <
mo...@wso2.com> wrot
On Mon, Jun 27, 2016 at 8:03 PM, Seshika Fernando wrote:
> Iranga,
> The optimization applies to siddhi queries that were written for IS
> analytics. Other product analytics would have different queries so this is
> not applicable there.
> This is not a siddhi level change, rather an optimization
Iranga,
The optimization applies to siddhi queries that were written for IS
analytics. Other product analytics would have different queries so this is
not applicable there.
This is not a siddhi level change, rather an optimization of the previously
written queries.
Seshi
On 27 Jun 2016 16:48, "Ira
On Mon, Jun 27, 2016 at 4:35 PM, Mohanadarshan Vivekanandalingam <
mo...@wso2.com> wrote:
>
>
> On Mon, Jun 27, 2016 at 4:30 PM, Seshika Fernando
> wrote:
>
>> Hey saith,
>>
>> This is great. So when you removed the duplicate windows, there were no
>> OOM issues?
>>
> Yes, we have introduced per-
On Mon, Jun 27, 2016 at 4:30 PM, Seshika Fernando wrote:
> Hey saith,
>
> This is great. So when you removed the duplicate windows, there were no
> OOM issues?
>
Yes, we have introduced per-second windows and eventually per-minute event
count get reduced. Then, there will not be an OOM..
Latest n
Hey saith,
This is great. So when you removed the duplicate windows, there were no OOM
issues?
Seshi
On 24 Jun 2016 14:28, "Sajith Ravindra" wrote:
> Hi Malith,
>
> Thanks for the explanation.
>>
>> I would expect some variation in the throughput. The aim should be
>> minimize the variation in
Hi Malith,
Thanks for the explanation.
>
> I would expect some variation in the throughput. The aim should be
> minimize the variation in the throughput (while maintaining the throughput
> at its highest level).
>
Agreed. Actually, our expectation is to minimize the fluctuation and to
increase th
Hi Sajith,
Thanks for the explanation.
I would expect some variation in the throughput. The aim should be minimize
the variation in the throughput (while maintaining the throughput at its
highest level).
It is possible to measure the latency as well?
regards
Malith
On Thu, Jun 23, 2016 at 1
Hi Malith,
The deployment is just a standalone DAS server, and we are planning to do a
test for HA deployment in recent future.
The workload is generated by a .csv data file which has 100K sample events,
10M events are generated by iterating through the same data set 100 times.
But we keep increa
Hi Sajith,
Could you please provide some details about how you are actually doing
these performance tests. For example, what is deployment model? How are
you generating these workloads/events?
Thanks
Malith
On Thu, Jun 23, 2016 at 11:28 AM, Sajith Ravindra wrote:
> Hi all,
>
> This is to giv
Hi all,
This is to give an update on the performance study we conducted on
is-analytics server on last. The idea of this test round was to evaluate
the performance of Siddhi queries used for is-analytics, therefore we
disabled event stream persistence and spark for this test.
This test was conduc
14 matches
Mail list logo
