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 2013/03/12 17:27:12 UTC

[jira] [Created] (UIMA-2735) Extend UIMA-AS deployment descriptor to allow disabling of JCAS caching

Jerry Cwiklik created UIMA-2735:
-----------------------------------

             Summary: Extend UIMA-AS deployment descriptor to allow disabling of JCAS caching
                 Key: UIMA-2735
                 URL: https://issues.apache.org/jira/browse/UIMA-2735
             Project: UIMA
          Issue Type: New Feature
          Components: Async Scaleout
    Affects Versions: 2.4.0AS
            Reporter: Jerry Cwiklik
            Assignee: Jerry Cwiklik
            Priority: Minor
             Fix For: 2.4.1AS


Modify UIMA-As deployment descriptor to support disabling of JCAS Cache on CasPool element. From the UIMA documentation:
 
"UIMAFramework.JCAS_CACHE_ENABLED: allows you to disable the JCas cache (true/false). The JCas cache is an internal datastructure that caches any JCas object created by the CAS. This may result in better performance for applications that make extensive use of the JCas, but also incurs a steep memory overhead. If you're processing large documents and have memory issues, you should disable this option. In general, just try running a few experiments to see what setting works better for your application. The JCas cache is enabled by default. "

To support this, the dd2spring needs to handle a new property in the DD - disableJCasCache=true/false on element casPool. Modify UIMA-AS CasManager wrapper to add setter and getter for the new property.

Also, changes are needed in DD Gui to support the new property


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira