activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "james strachan (JIRA)" <j...@apache.org>
Subject [jira] Updated: (AMQ-792) allow asynchronous dispatch to consumers in the broker for non-durable topics
Date Mon, 03 Jul 2006 18:47:51 GMT
     [ https://issues.apache.org/activemq/browse/AMQ-792?page=all ]

james strachan updated AMQ-792:
-------------------------------

    Description: 
We typically use the current thread in the broker to dispatch to all the available non-durable
consumers for performance - as this hugely reduces the context switching and increases performance.
However (see AMQ-688) sometimes this can cause one dead consumer to block a producer.

Some folks may want to switch this strategy to use slower asynchronous dispatch with a thread
pool to reduce the risk of blocking a producer at the expensive of lower performance

  was:
We typically use a single thread in the producer to dispatch to all the available non-durable
consumers for performance - as this hugely reduces the context switching and increases performance.
However (see AMQ-688) sometimes this can cause one dead consumer to block a producer.

Some folks may want to switch this strategy to use slower asynchronous dispatch with a thread
pool to reduce the risk of blocking a producer at the expensive of lower performance


> allow asynchronous dispatch to consumers in the broker for non-durable topics
> -----------------------------------------------------------------------------
>
>          Key: AMQ-792
>          URL: https://issues.apache.org/activemq/browse/AMQ-792
>      Project: ActiveMQ
>         Type: Improvement

>   Components: Broker
>     Reporter: james strachan
>      Fix For: 4.2

>
>
> We typically use the current thread in the broker to dispatch to all the available non-durable
consumers for performance - as this hugely reduces the context switching and increases performance.
However (see AMQ-688) sometimes this can cause one dead consumer to block a producer.
> Some folks may want to switch this strategy to use slower asynchronous dispatch with
a thread pool to reduce the risk of blocking a producer at the expensive of lower performance

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message