[
https://issues.apache.org/jira/browse/FELIX-1913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12784727#action_12784727
]
Carsten Ziegeler commented on FELIX-1913:
-----------------------------------------
Ups, yepp, I agree its not a major bug (just used the default....) and yes its
more an improvement :)
Ok, yes, I'm talking about synchronous events. If two different threads send an
event synchronous, these events are both put into a queue (well in fact the
event handlers are put into the queue) and then processed one after the other.
I think in this case, the events could be processed in parallel.
The current queueing might block threads sending events synchronously with a
high volume of events - now I agree that in most cases async delivery could be
used to not block the threads.
The underlying problem is that we are using the event admin for all kinds of
notifications - and with a high volume of events the notifications get very
slow.
> All synchronous events are processed in one queue
> -------------------------------------------------
>
> Key: FELIX-1913
> URL: https://issues.apache.org/jira/browse/FELIX-1913
> Project: Felix
> Issue Type: Improvement
> Components: Event Admin
> Affects Versions: eventadmin 1.0.0
> Reporter: Carsten Ziegeler
> Assignee: Karl Pauls
> Priority: Minor
>
> The current event admin implementation puts all events into one single queue
> and processes this queue is in one thread. This creates a bottleneck when
> different threads send events as they have to wait for other threads to be
> processed first. Events from different threads can be processed in parallel.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
