You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@felix.apache.org by Vlatko Davidovski <vd...@gmail.com> on 2010/01/18 04:14:03 UTC
iPojo Event admin handling
Hi!
Has anyone evaluated the performance of iPojo Event admin handling? Is
there any limited maximum number of events/data that can be sent per
second.
When sending significant amount of events, I experienced that they
don't arrive at the subscriber method. On the other hand, everything
seems to be working under low load.
Any recommendations? Is it better to use synchronous or asynchronous
delivery under such circumstances?
Thanks,
Vlatko
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org
Re: iPojo Event admin handling
Posted by Vlatko Davidovski <vd...@gmail.com>.
Thanks Carsten!
This was really helpful!
Regards,
Vlatko
On Jan 18, 2010, at 5:30 PM, Carsten Ziegeler wrote:
> Vlatko Davidovski wrote:
>> Thanks for the info Carsten.
>>
>> However, can I turn off the blacklisting as well as set the maximum
>> number of parallel workers in Apache Felix Event Admin?
>>
> Yes, you can turn off the blacklisting, see here:
> http://osdir.com/ml/users-felix-apache/2009-02/msg00172.html
>
> Turning of the blacklisting ensures that your handlers never get in
> the
> blacklist again - however if you have a faulty handler (which never
> returns) this might create new problems.
>
>
> There is also the org.apache.felix.eventadmin.ThreadPoolSize
> property to
> set the thread pool size - however I'm not sure if this - with the
> current implementation - really improves performance.
>
> Regards
> Carsten
> --
> Carsten Ziegeler
> cziegeler@apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> For additional commands, e-mail: users-help@felix.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org
Re: iPojo Event admin handling
Posted by Carsten Ziegeler <cz...@apache.org>.
Vlatko Davidovski wrote:
> Thanks for the info Carsten.
>
> However, can I turn off the blacklisting as well as set the maximum
> number of parallel workers in Apache Felix Event Admin?
>
Yes, you can turn off the blacklisting, see here:
http://osdir.com/ml/users-felix-apache/2009-02/msg00172.html
Turning of the blacklisting ensures that your handlers never get in the
blacklist again - however if you have a faulty handler (which never
returns) this might create new problems.
There is also the org.apache.felix.eventadmin.ThreadPoolSize property to
set the thread pool size - however I'm not sure if this - with the
current implementation - really improves performance.
Regards
Carsten
--
Carsten Ziegeler
cziegeler@apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org
Re: iPojo Event admin handling
Posted by Vlatko Davidovski <vd...@gmail.com>.
Thanks for the info Carsten.
However, can I turn off the blacklisting as well as set the maximum
number of parallel workers in Apache Felix Event Admin?
Regards,
Vlatko
On Jan 18, 2010, at 3:48 PM, Carsten Ziegeler wrote:
> Marcel Offermans wrote:
>> On Jan 18, 2010, at 4:14 , Vlatko Davidovski wrote:
>>
>>> Has anyone evaluated the performance of iPojo Event admin
>>> handling? Is there any limited maximum number of events/data that
>>> can be sent per second.
>>> When sending significant amount of events, I experienced that they
>>> don't arrive at the subscriber method. On the other hand,
>>> everything seems to be working under low load.
>>
>> Ik know Carsten has recently been working on Event Admin
>> performance in general, so no doubt he has done a lot of
>> performance testing. I never tried iPOJOs Event Admin support but
>> in general I know that if things slow down too much, handlers can
>> get blacklisted and won't be notified anymore. This behaviour is
>> configurable, and can even be turned off if you don't want it.
>>
>>> Any recommendations? Is it better to use synchronous or
>>> asynchronous delivery under such circumstances?
>>
>> Asynchronous should be faster. I think even the spec mentions that
>> you should prefer them over synchronous events.
>>
> Yes, the spec mentions this - if we're speaking of the standard felix
> event admin, there is FELIX-1913 to improve the performance where
> possible. We had a lot of trouble with the event admin under heavy
> load
> (several threads sending lots of events at the same time). The bug is
> about to fix this - once we have this, I currently see some other
> areas
> where we could improve the implementation.
>
> Regards
> Carsten
> --
> Carsten Ziegeler
> cziegeler@apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> For additional commands, e-mail: users-help@felix.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org
Re: iPojo Event admin handling
Posted by Carsten Ziegeler <cz...@apache.org>.
Marcel Offermans wrote:
> On Jan 18, 2010, at 4:14 , Vlatko Davidovski wrote:
>
>> Has anyone evaluated the performance of iPojo Event admin handling? Is there any limited maximum number of events/data that can be sent per second.
>> When sending significant amount of events, I experienced that they don't arrive at the subscriber method. On the other hand, everything seems to be working under low load.
>
> Ik know Carsten has recently been working on Event Admin performance in general, so no doubt he has done a lot of performance testing. I never tried iPOJOs Event Admin support but in general I know that if things slow down too much, handlers can get blacklisted and won't be notified anymore. This behaviour is configurable, and can even be turned off if you don't want it.
>
>> Any recommendations? Is it better to use synchronous or asynchronous delivery under such circumstances?
>
> Asynchronous should be faster. I think even the spec mentions that you should prefer them over synchronous events.
>
Yes, the spec mentions this - if we're speaking of the standard felix
event admin, there is FELIX-1913 to improve the performance where
possible. We had a lot of trouble with the event admin under heavy load
(several threads sending lots of events at the same time). The bug is
about to fix this - once we have this, I currently see some other areas
where we could improve the implementation.
Regards
Carsten
--
Carsten Ziegeler
cziegeler@apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org
Re: iPojo Event admin handling
Posted by Vlatko Davidovski <vd...@gmail.com>.
Thanks Marcel and Clement!
This explains a lot.
The reason that probably a blacklisting happens is because I basically
bombard the system with events, so seems like after some threshold
messages stop being delivered.
Could you give me a hint how to disable the blacklisting?
Regards,
Vlatko
On Jan 18, 2010, at 7:38 AM, Clement Escoffier wrote:
> Hi,
>
> The Event Admin handler test suite has a test case sending an event
> storm and checking the reception of all of them (in async mode). In
> synchronization mode, it might be possible that the event handlers
> become blacklisted (if they don't return 'quickly').
>
> So first, check if your handler are not blacklisted (it is possible
> to disable this event admin feature).
> Then try the asynchronous mode.
>
> If you see a strange behavior inside the handler, feel free to open
> a jira issue. We will look into it.
>
> Regards,
>
> Clement
>
> On 18.01.2010, at 07:12, Marcel Offermans wrote:
>
>> On Jan 18, 2010, at 4:14 , Vlatko Davidovski wrote:
>>
>>> Has anyone evaluated the performance of iPojo Event admin
>>> handling? Is there any limited maximum number of events/data that
>>> can be sent per second.
>>> When sending significant amount of events, I experienced that they
>>> don't arrive at the subscriber method. On the other hand,
>>> everything seems to be working under low load.
>>
>> Ik know Carsten has recently been working on Event Admin
>> performance in general, so no doubt he has done a lot of
>> performance testing. I never tried iPOJOs Event Admin support but
>> in general I know that if things slow down too much, handlers can
>> get blacklisted and won't be notified anymore. This behaviour is
>> configurable, and can even be turned off if you don't want it.
>>
>>> Any recommendations? Is it better to use synchronous or
>>> asynchronous delivery under such circumstances?
>>
>> Asynchronous should be faster. I think even the spec mentions that
>> you should prefer them over synchronous events.
>>
>> Greetings, Marcel
>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>> For additional commands, e-mail: users-help@felix.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> For additional commands, e-mail: users-help@felix.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org
Re: iPojo Event admin handling
Posted by Vlatko Davidovski <vd...@gmail.com>.
I found that some other implementation of EventAdmin has this
properties:
http://dz.prosyst.com/pdoc/mbs_prof_6.1/um/framework/bundles/osgi/eventadmin/eventadmin.html
Where could I find similar documentation on the Apache Felix EventAdmin?
Would be great to also have the possibility to set a maximum number of
workers and queues besides turning off the blacklisting.
Thanks!
Vlatko
On Jan 18, 2010, at 7:38 AM, Clement Escoffier wrote:
> Hi,
>
> The Event Admin handler test suite has a test case sending an event
> storm and checking the reception of all of them (in async mode). In
> synchronization mode, it might be possible that the event handlers
> become blacklisted (if they don't return 'quickly').
>
> So first, check if your handler are not blacklisted (it is possible
> to disable this event admin feature).
> Then try the asynchronous mode.
>
> If you see a strange behavior inside the handler, feel free to open
> a jira issue. We will look into it.
>
> Regards,
>
> Clement
>
> On 18.01.2010, at 07:12, Marcel Offermans wrote:
>
>> On Jan 18, 2010, at 4:14 , Vlatko Davidovski wrote:
>>
>>> Has anyone evaluated the performance of iPojo Event admin
>>> handling? Is there any limited maximum number of events/data that
>>> can be sent per second.
>>> When sending significant amount of events, I experienced that they
>>> don't arrive at the subscriber method. On the other hand,
>>> everything seems to be working under low load.
>>
>> Ik know Carsten has recently been working on Event Admin
>> performance in general, so no doubt he has done a lot of
>> performance testing. I never tried iPOJOs Event Admin support but
>> in general I know that if things slow down too much, handlers can
>> get blacklisted and won't be notified anymore. This behaviour is
>> configurable, and can even be turned off if you don't want it.
>>
>>> Any recommendations? Is it better to use synchronous or
>>> asynchronous delivery under such circumstances?
>>
>> Asynchronous should be faster. I think even the spec mentions that
>> you should prefer them over synchronous events.
>>
>> Greetings, Marcel
>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>> For additional commands, e-mail: users-help@felix.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> For additional commands, e-mail: users-help@felix.apache.org
>
Re: iPojo Event admin handling
Posted by Clement Escoffier <cl...@gmail.com>.
Hi,
The Event Admin handler test suite has a test case sending an event storm and checking the reception of all of them (in async mode). In synchronization mode, it might be possible that the event handlers become blacklisted (if they don't return 'quickly').
So first, check if your handler are not blacklisted (it is possible to disable this event admin feature).
Then try the asynchronous mode.
If you see a strange behavior inside the handler, feel free to open a jira issue. We will look into it.
Regards,
Clement
On 18.01.2010, at 07:12, Marcel Offermans wrote:
> On Jan 18, 2010, at 4:14 , Vlatko Davidovski wrote:
>
>> Has anyone evaluated the performance of iPojo Event admin handling? Is there any limited maximum number of events/data that can be sent per second.
>> When sending significant amount of events, I experienced that they don't arrive at the subscriber method. On the other hand, everything seems to be working under low load.
>
> Ik know Carsten has recently been working on Event Admin performance in general, so no doubt he has done a lot of performance testing. I never tried iPOJOs Event Admin support but in general I know that if things slow down too much, handlers can get blacklisted and won't be notified anymore. This behaviour is configurable, and can even be turned off if you don't want it.
>
>> Any recommendations? Is it better to use synchronous or asynchronous delivery under such circumstances?
>
> Asynchronous should be faster. I think even the spec mentions that you should prefer them over synchronous events.
>
> Greetings, Marcel
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> For additional commands, e-mail: users-help@felix.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org
Re: iPojo Event admin handling
Posted by Marcel Offermans <ma...@luminis.nl>.
On Jan 18, 2010, at 4:14 , Vlatko Davidovski wrote:
> Has anyone evaluated the performance of iPojo Event admin handling? Is there any limited maximum number of events/data that can be sent per second.
> When sending significant amount of events, I experienced that they don't arrive at the subscriber method. On the other hand, everything seems to be working under low load.
Ik know Carsten has recently been working on Event Admin performance in general, so no doubt he has done a lot of performance testing. I never tried iPOJOs Event Admin support but in general I know that if things slow down too much, handlers can get blacklisted and won't be notified anymore. This behaviour is configurable, and can even be turned off if you don't want it.
> Any recommendations? Is it better to use synchronous or asynchronous delivery under such circumstances?
Asynchronous should be faster. I think even the spec mentions that you should prefer them over synchronous events.
Greetings, Marcel
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org