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
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
