You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Jerry Cwiklik (JIRA)" <de...@uima.apache.org> on 2010/06/04 15:58:55 UTC
[jira] Created: (UIMA-1799) UIMA AS should provide a way to
increase prefetch size on a reply queue
UIMA AS should provide a way to increase prefetch size on a reply queue
-----------------------------------------------------------------------
Key: UIMA-1799
URL: https://issues.apache.org/jira/browse/UIMA-1799
Project: UIMA
Issue Type: Improvement
Components: Async Scaleout
Affects Versions: 2.3AS
Reporter: Jerry Cwiklik
Assignee: Jerry Cwiklik
UIMA AS currently provides no way to change prefetch size on a reply queue. A default of 1 is used. This slows down the rate of processing messages by a service. Each UIMA AS service has a dedicated submitter thread whose main job is to deliver a message to a thread pool for processing. Since the submitter thread executes very fast and the prefetch=1 , the submitter thread is constantly waiting for the Broker to deliver the next message. Increasing prefetch forces the Broker to deliver multiple messages to a service which buffers them until the submitter thread is ready. The size of the prefetch should be equal to a scalout factor defined on each reply queue. The default is still 1.
NOTE: increasing prefetch effects memory requirement for the service. The larger the prefetch the more messages are buffered taking up more memory.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (UIMA-1799) UIMA AS should provide a way to increase
prefetch size on a reply queue
Posted by "Jerry Cwiklik (JIRA)" <de...@uima.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-1799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jerry Cwiklik closed UIMA-1799.
-------------------------------
Resolution: Fixed
Modified UIMA AS listener code to override prefetch on a reply queue. The override value comes from the scaleout factor defined on a reply queue in the deployment descriptor.
> UIMA AS should provide a way to increase prefetch size on a reply queue
> -----------------------------------------------------------------------
>
> Key: UIMA-1799
> URL: https://issues.apache.org/jira/browse/UIMA-1799
> Project: UIMA
> Issue Type: Improvement
> Components: Async Scaleout
> Affects Versions: 2.3AS
> Reporter: Jerry Cwiklik
> Assignee: Jerry Cwiklik
>
> UIMA AS currently provides no way to change prefetch size on a reply queue. A default of 1 is used. This slows down the rate of processing messages by a service. Each UIMA AS service has a dedicated submitter thread whose main job is to deliver a message to a thread pool for processing. Since the submitter thread executes very fast and the prefetch=1 , the submitter thread is constantly waiting for the Broker to deliver the next message. Increasing prefetch forces the Broker to deliver multiple messages to a service which buffers them until the submitter thread is ready. The size of the prefetch should be equal to a scalout factor defined on each reply queue. The default is still 1.
> NOTE: increasing prefetch effects memory requirement for the service. The larger the prefetch the more messages are buffered taking up more memory.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (UIMA-1799) UIMA AS should provide a way to increase
prefetch size on a reply queue
Posted by "Jerry Cwiklik (JIRA)" <de...@uima.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-1799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jerry Cwiklik closed UIMA-1799.
-------------------------------
Resolution: Fixed
Uncommented code in UimaDefaultMessageListenerContainer.setDestination() that registers temp queue listener with InputChannel.
> UIMA AS should provide a way to increase prefetch size on a reply queue
> -----------------------------------------------------------------------
>
> Key: UIMA-1799
> URL: https://issues.apache.org/jira/browse/UIMA-1799
> Project: UIMA
> Issue Type: Improvement
> Components: Async Scaleout
> Affects Versions: 2.3AS
> Reporter: Jerry Cwiklik
> Assignee: Jerry Cwiklik
>
> UIMA AS currently provides no way to change prefetch size on a reply queue. A default of 1 is used. This slows down the rate of processing messages by a service. Each UIMA AS service has a dedicated submitter thread whose main job is to deliver a message to a thread pool for processing. Since the submitter thread executes very fast and the prefetch=1 , the submitter thread is constantly waiting for the Broker to deliver the next message. Increasing prefetch forces the Broker to deliver multiple messages to a service which buffers them until the submitter thread is ready. The size of the prefetch should be equal to a scalout factor defined on each reply queue. The default is still 1.
> NOTE: increasing prefetch effects memory requirement for the service. The larger the prefetch the more messages are buffered taking up more memory.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-1799) UIMA AS should provide a way to
increase prefetch size on a reply queue
Posted by "Marshall Schor (JIRA)" <de...@uima.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-1799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marshall Schor updated UIMA-1799:
---------------------------------
Fix Version/s: 2.3.1AS
> UIMA AS should provide a way to increase prefetch size on a reply queue
> -----------------------------------------------------------------------
>
> Key: UIMA-1799
> URL: https://issues.apache.org/jira/browse/UIMA-1799
> Project: UIMA
> Issue Type: Improvement
> Components: Async Scaleout
> Affects Versions: 2.3AS
> Reporter: Jerry Cwiklik
> Assignee: Jerry Cwiklik
> Fix For: 2.3.1AS
>
>
> UIMA AS currently provides no way to change prefetch size on a reply queue. A default of 1 is used. This slows down the rate of processing messages by a service. Each UIMA AS service has a dedicated submitter thread whose main job is to deliver a message to a thread pool for processing. Since the submitter thread executes very fast and the prefetch=1 , the submitter thread is constantly waiting for the Broker to deliver the next message. Increasing prefetch forces the Broker to deliver multiple messages to a service which buffers them until the submitter thread is ready. The size of the prefetch should be equal to a scalout factor defined on each reply queue. The default is still 1.
> NOTE: increasing prefetch effects memory requirement for the service. The larger the prefetch the more messages are buffered taking up more memory.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Reopened: (UIMA-1799) UIMA AS should provide a way to
increase prefetch size on a reply queue
Posted by "Jerry Cwiklik (JIRA)" <de...@uima.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-1799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jerry Cwiklik reopened UIMA-1799:
---------------------------------
Accidentally commented out a chunk of code that registers temp queue listener with InputChannel. This leads to a hang when stopping a service using JMX or from a command line.
> UIMA AS should provide a way to increase prefetch size on a reply queue
> -----------------------------------------------------------------------
>
> Key: UIMA-1799
> URL: https://issues.apache.org/jira/browse/UIMA-1799
> Project: UIMA
> Issue Type: Improvement
> Components: Async Scaleout
> Affects Versions: 2.3AS
> Reporter: Jerry Cwiklik
> Assignee: Jerry Cwiklik
>
> UIMA AS currently provides no way to change prefetch size on a reply queue. A default of 1 is used. This slows down the rate of processing messages by a service. Each UIMA AS service has a dedicated submitter thread whose main job is to deliver a message to a thread pool for processing. Since the submitter thread executes very fast and the prefetch=1 , the submitter thread is constantly waiting for the Broker to deliver the next message. Increasing prefetch forces the Broker to deliver multiple messages to a service which buffers them until the submitter thread is ready. The size of the prefetch should be equal to a scalout factor defined on each reply queue. The default is still 1.
> NOTE: increasing prefetch effects memory requirement for the service. The larger the prefetch the more messages are buffered taking up more memory.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.