Reputation: 237
I have tested HTTP receiver with both WSO2 CEP 4.1.0 & 4.2.0. With same set of data, streams, execution plan(just event count wit 1 min window), publisher(logger) 4.1.0 is able to process 1M/minute but 4.2.0 could go up to 200K-300K/minute.
Have conducted the same test with my custom file receiver and found similar result as above.
By the way, I have tested it on my laptop, 3 MB file with 10 Millions records.
Thanks, Obaid
Upvotes: 2
Views: 96
Reputation: 237
Just completed the test and have a feeling that logger publisher in 4.2.0 is the culprit here. Please find below outcomes and share your opinion (M=Million):
HTTP Receiver only push to Event Stream:
HTTP Receiver + below execution plan + logger:
HTTP Receiver + below execution plan + "NO" logger:
Custom File Receiver + below execution plan + "NO" logger:
@Import('subsApps:1.0.0')
define stream subsApps (meta_app_name string, correlation_imsi long, volume double);
@Export('subsCount:1.0.0')
define stream subsCount (meta_counts long);
from subsApps#window.time( 1 min )
select count() as meta_counts
insert into subsCount;
Upvotes: 3
Reputation: 2510
This could not happen from HTTP receiver end, according to source codes of carbon-analyics-common packed with 4.1.0 [1] and 4.2.0 [2] there are no significant changes. The only change is if checking added for basic auth. This could be some other issue. Specially we can check on execution plan as well. its better if you could try to do same test by using wso2event adapter which does not have any changes in source codes of carbon-analyics-common packed with 4.1.0 [3] and 4.2.0 [4].
Upvotes: 0