You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Marshall Schor (JIRA)" <ui...@incubator.apache.org> on 2008/08/27 17:39:44 UTC
[jira] Created: (UIMA-1161) UIMA-AS inputQueueScaleout should be
settable on nested co-located aggregates
UIMA-AS inputQueueScaleout should be settable on nested co-located aggregates
-----------------------------------------------------------------------------
Key: UIMA-1161
URL: https://issues.apache.org/jira/browse/UIMA-1161
Project: UIMA
Issue Type: Bug
Components: Async Scaleout
Reporter: Marshall Schor
Assignee: Marshall Schor
Priority: Minor
My initial thinking about this reasoned that for co-located nested aggregates, their input queues would not need any scaleout because there would be no deserialization (the input queue passes a handle instead of a serialized CAS for co-located nested aggregates). And also, no re-serialization back to the invoker (again, just a handle is passed).
However, Eddie has pointed out that if the nested aggregate has a remote delegate as its first component, then the serialization work going to that delegate is done using the thread on the input queue listener.
Also, I note that if the flow controller work requires any significant time, scaleout might be needed, as the input queue listener thread is used for the first entry into the flow controller (subsequent entries into the flow controller run on the aggregate's reply queue listeners).
Because of this, we should allow the inputQueueScaleout parameter on nested aggregates, as well as just on the top level one.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (UIMA-1161) UIMA-AS inputQueueScaleout should be
settable on nested co-located aggregates
Posted by "Marshall Schor (JIRA)" <ui...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-1161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marshall Schor closed UIMA-1161.
--------------------------------
Resolution: Fixed
Fix Version/s: 2.3AS
> UIMA-AS inputQueueScaleout should be settable on nested co-located aggregates
> -----------------------------------------------------------------------------
>
> Key: UIMA-1161
> URL: https://issues.apache.org/jira/browse/UIMA-1161
> Project: UIMA
> Issue Type: Bug
> Components: Async Scaleout
> Reporter: Marshall Schor
> Assignee: Marshall Schor
> Priority: Minor
> Fix For: 2.3AS
>
>
> My initial thinking about this reasoned that for co-located nested aggregates, their input queues would not need any scaleout because there would be no deserialization (the input queue passes a handle instead of a serialized CAS for co-located nested aggregates). And also, no re-serialization back to the invoker (again, just a handle is passed).
> However, Eddie has pointed out that if the nested aggregate has a remote delegate as its first component, then the serialization work going to that delegate is done using the thread on the input queue listener.
> Also, I note that if the flow controller work requires any significant time, scaleout might be needed, as the input queue listener thread is used for the first entry into the flow controller (subsequent entries into the flow controller run on the aggregate's reply queue listeners).
> Because of this, we should allow the inputQueueScaleout parameter on nested aggregates, as well as just on the top level one.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.