[
https://issues.apache.org/jira/browse/FELIX-1913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler updated FELIX-1913:
------------------------------------
Description:
The current event admin implementation puts all events into a queue and
processes this queue 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.
In the async mode, event deliver might take a long time as these events are
processed one after the other as well.
was: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.
Summary: All events are processed in a queue (was: All synchronous
events are processed in one queue)
> All events are processed in a 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
> Attachments: ea.patch
>
>
> The current event admin implementation puts all events into a queue and
> processes this queue 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.
> In the async mode, event deliver might take a long time as these events are
> processed one after the other as well.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
