You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Thomas Hampp (JIRA)" <ui...@incubator.apache.org> on 2009/07/07 17:07:14 UTC
[jira] Created: (UIMA-1426) More control for apps against OOMs from
UIMA core: Add configuration option to set the maximum heap size the CAS
will grow to
More control for apps against OOMs from UIMA core: Add configuration option to set the maximum heap size the CAS will grow to
-----------------------------------------------------------------------------------------------------------------------------
Key: UIMA-1426
URL: https://issues.apache.org/jira/browse/UIMA-1426
Project: UIMA
Issue Type: Improvement
Components: Core Java Framework
Reporter: Thomas Hampp
Applications need to protect themselves against out of memory exceptions (OOMs). UIMA should help with that by making sure a growth in the CAS heap size will not cause an OOM. One way to do this is to add a config param that controls the maximum heap size for a CAS and throw a runtime exception if that threshold is exceeded.
Since apps often use multiple CASes in pools in multihreaded fashion they would still need to exercise some app specific math (and guesswork) to determine the right value for this param. But at least they would be able to have some control.
(There could still be OOMs during UIMA processing from other sources)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (UIMA-1426) More control for apps against OOMs
from UIMA core: Add configuration option to set the maximum heap size the
CAS will grow to
Posted by "Thilo Goetz (JIRA)" <ui...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-1426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12742225#action_12742225 ]
Thilo Goetz commented on UIMA-1426:
-----------------------------------
No, let's leave open (unless somebody else wants a go).
> More control for apps against OOMs from UIMA core: Add configuration option to set the maximum heap size the CAS will grow to
> -----------------------------------------------------------------------------------------------------------------------------
>
> Key: UIMA-1426
> URL: https://issues.apache.org/jira/browse/UIMA-1426
> Project: UIMA
> Issue Type: Improvement
> Components: Core Java Framework
> Reporter: Thomas Hampp
>
> Applications need to protect themselves against out of memory exceptions (OOMs). UIMA should help with that by making sure a growth in the CAS heap size will not cause an OOM. One way to do this is to add a config param that controls the maximum heap size for a CAS and throw a runtime exception if that threshold is exceeded.
> Since apps often use multiple CASes in pools in multihreaded fashion they would still need to exercise some app specific math (and guesswork) to determine the right value for this param. But at least they would be able to have some control.
> (There could still be OOMs during UIMA processing from other sources)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-1426) More control for apps against OOMs from
UIMA core: Add configuration option to set the maximum heap size the CAS
will grow to
Posted by "Marshall Schor (JIRA)" <ui...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-1426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marshall Schor updated UIMA-1426:
---------------------------------
Affects Version/s: 2.3
marking as "affects 2.3" to indicate not being fixed this cycle.
> More control for apps against OOMs from UIMA core: Add configuration option to set the maximum heap size the CAS will grow to
> -----------------------------------------------------------------------------------------------------------------------------
>
> Key: UIMA-1426
> URL: https://issues.apache.org/jira/browse/UIMA-1426
> Project: UIMA
> Issue Type: Improvement
> Components: Core Java Framework
> Affects Versions: 2.3
> Reporter: Thomas Hampp
>
> Applications need to protect themselves against out of memory exceptions (OOMs). UIMA should help with that by making sure a growth in the CAS heap size will not cause an OOM. One way to do this is to add a config param that controls the maximum heap size for a CAS and throw a runtime exception if that threshold is exceeded.
> Since apps often use multiple CASes in pools in multihreaded fashion they would still need to exercise some app specific math (and guesswork) to determine the right value for this param. But at least they would be able to have some control.
> (There could still be OOMs during UIMA processing from other sources)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (UIMA-1426) More control for apps against OOMs
from UIMA core: Add configuration option to set the maximum heap size the
CAS will grow to
Posted by "Marshall Schor (JIRA)" <ui...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-1426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12742177#action_12742177 ]
Marshall Schor commented on UIMA-1426:
--------------------------------------
Thilo - were you going to be working on this? Is it something that you could do in time for the 2.3.0 release?
> More control for apps against OOMs from UIMA core: Add configuration option to set the maximum heap size the CAS will grow to
> -----------------------------------------------------------------------------------------------------------------------------
>
> Key: UIMA-1426
> URL: https://issues.apache.org/jira/browse/UIMA-1426
> Project: UIMA
> Issue Type: Improvement
> Components: Core Java Framework
> Reporter: Thomas Hampp
>
> Applications need to protect themselves against out of memory exceptions (OOMs). UIMA should help with that by making sure a growth in the CAS heap size will not cause an OOM. One way to do this is to add a config param that controls the maximum heap size for a CAS and throw a runtime exception if that threshold is exceeded.
> Since apps often use multiple CASes in pools in multihreaded fashion they would still need to exercise some app specific math (and guesswork) to determine the right value for this param. But at least they would be able to have some control.
> (There could still be OOMs during UIMA processing from other sources)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.