[
https://issues.apache.org/jira/browse/UIMA-1130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12620271#action_12620271
]
Adam Lally commented on UIMA-1130:
----------------------------------
I think Eddie is probably right that increasing the number of listeners should
eliminate my need to set a prefetch > 0. A thread that's being used to execute
prefetch isn't doing anything that an additional listener thread wouldn't also
do, as far as I understand it. So I'm +1 to proceed with the plan as Eddie
outlined it.
> Deployment Descriptor should allow setting the number of concurrent listeners
> for a reply queue
> -----------------------------------------------------------------------------------------------
>
> Key: UIMA-1130
> URL: https://issues.apache.org/jira/browse/UIMA-1130
> Project: UIMA
> Issue Type: Improvement
> Components: Async Scaleout
> Affects Versions: 2.2.2
> Reporter: Adam Lally
>
> The Spring XML allows setting a concurrentConsumers property for a reply
> queue (either an aggregate's collocated reply queue or a remote reply queue):
> <property name="concurrentConsumers" value="1"/>
> The deployment descriptor should allow setting this property. In some
> deployments where remote delegates are scaled out many times, the bottleneck
> can become the aggregate deserializing CASes from the reply queue. If the
> aggregate is running on a multicore machine it helps to increase the number
> of threads that can process the reply queue.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
