You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Bhavani Iyer (JIRA)" <ui...@incubator.apache.org> on 2009/11/13 19:09:39 UTC
[jira] Created: (UIMA-1666) CasPoolSize should equal
numberOfInstances when deploying a primitive component
CasPoolSize should equal numberOfInstances when deploying a primitive component
-------------------------------------------------------------------------------
Key: UIMA-1666
URL: https://issues.apache.org/jira/browse/UIMA-1666
Project: UIMA
Issue Type: Bug
Components: Async Scaleout
Reporter: Bhavani Iyer
When deploying a primitive component, the cas pool size should equal the number of instances. If a user explicitly sets the cas pool size in the deployement descriptor, it should be overridden and set to the number of instances and a warning log message written. If set to less than the number of instance, the user does not get the expected performance improvement and its too easy to get this wrong.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (UIMA-1666) CasPoolSize should equal
numberOfInstances when deploying a primitive component
Posted by "Marshall Schor (JIRA)" <ui...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-1666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12777642#action_12777642 ]
Marshall Schor commented on UIMA-1666:
--------------------------------------
I agree that warnings can be overlooked. In this case, since we "recover" this error with no adverse consequences, I don't see the value in not starting.
We can add a comment that if the user is trying to control the size of the pool because otherwise too much memory is used, they must do it by changing the number of instances.
The <caspool> element is needed to specify the initial CAS heap size, so the user might have this element for a legitimate reason.
-Marshall
> CasPoolSize should equal numberOfInstances when deploying a primitive component
> -------------------------------------------------------------------------------
>
> Key: UIMA-1666
> URL: https://issues.apache.org/jira/browse/UIMA-1666
> Project: UIMA
> Issue Type: Bug
> Components: Async Scaleout
> Reporter: Bhavani Iyer
>
> When deploying a primitive component, the cas pool size should equal the number of instances. If a user explicitly sets the cas pool size in the deployement descriptor, it should be overridden and set to the number of instances and a warning log message written. If set to less than the number of instance, the user does not get the expected performance improvement and its too easy to get this wrong.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (UIMA-1666) CasPoolSize should equal
numberOfInstances when deploying a primitive component
Posted by "Jörn Kottmann (JIRA)" <ui...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-1666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12777594#action_12777594 ]
Jörn Kottmann commented on UIMA-1666:
-------------------------------------
Warnings are easily overseen, wouldn't it be better to not start at all if this setting is wrong ?
> CasPoolSize should equal numberOfInstances when deploying a primitive component
> -------------------------------------------------------------------------------
>
> Key: UIMA-1666
> URL: https://issues.apache.org/jira/browse/UIMA-1666
> Project: UIMA
> Issue Type: Bug
> Components: Async Scaleout
> Reporter: Bhavani Iyer
>
> When deploying a primitive component, the cas pool size should equal the number of instances. If a user explicitly sets the cas pool size in the deployement descriptor, it should be overridden and set to the number of instances and a warning log message written. If set to less than the number of instance, the user does not get the expected performance improvement and its too easy to get this wrong.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (UIMA-1666) CasPoolSize should equal
numberOfInstances when deploying a primitive component
Posted by "Marshall Schor (JIRA)" <ui...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-1666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marshall Schor resolved UIMA-1666.
----------------------------------
Resolution: Fixed
Fix Version/s: 2.3AS
Assignee: Marshall Schor
Bhavani, can you verify this fix?
> CasPoolSize should equal numberOfInstances when deploying a primitive component
> -------------------------------------------------------------------------------
>
> Key: UIMA-1666
> URL: https://issues.apache.org/jira/browse/UIMA-1666
> Project: UIMA
> Issue Type: Bug
> Components: Async Scaleout
> Reporter: Bhavani Iyer
> Assignee: Marshall Schor
> Fix For: 2.3AS
>
>
> When deploying a primitive component, the cas pool size should equal the number of instances. If a user explicitly sets the cas pool size in the deployement descriptor, it should be overridden and set to the number of instances and a warning log message written. If set to less than the number of instance, the user does not get the expected performance improvement and its too easy to get this wrong.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.