Hi Asok,

Siddhi 2.x.x implementations use [1] to achieve synchronization. In current
implementation, process method will be accessed by multiple threads. So in
custom implementations you need to handle that accordingly.
So the maximum memory for event queue will be actually decided by jvm. Also
defining an acceptable processing time per single event is not feasible.
There are many more decisive factors like message size.
So when writing custom functions/extension/etc you should make sure
process() is fully optimized since it will be a part of main execution
flow. Avoid new object creation as far as possible. Utilize init()
effectively to perform required configurations.

[1]
http://docs.oracle.com/javase/6/docs/api/java/util/concurrent/locks/Lock.html

On Fri, Oct 17, 2014 at 7:14 PM, Asok Perera <[email protected]> wrote:

> Hi,
>
> Could I know how the Event queuing (Not referring to the window extension)
> happens in Siddhi whenever there is synchronised method in a class which is
> called through siddhi extension (Say transformer extension) ?
>
> The exact case I'm referring here is, there is a function which consumes
> some time and this same function needs to be synchronised as it refers to
> the previous results when performing the calculation. So because of this,
> the events will be queued until the previous event is processed.
>
> The specifics I need to know are, what will be the maximum Memory for
> Event queue in siddhi (in case if it is limited by siddhi, below Java max
> heap size), and what will be the accepted processing time per single event ?
>
> BR
>
> *Asok Aravinda Perera*
> Software Engineer
> WSO2, Inc.;http://wso2.com/
> <http://www.google.com/url?q=http%3A%2F%2Fwso2.com%2F&sa=D&sntz=1&usg=AFQjCNGJuLRux6KkJwXKVUCYOtEsNCmIAQ>
> lean.enterprise.middleware
>
> Mobile: +94722241032
>
> _______________________________________________
> Dev mailing list
> [email protected]
> 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.
_______________________________________________
Dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/dev

Reply via email to