You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Thilo Goetz (JIRA)" <ui...@incubator.apache.org> on 2007/09/18 14:10:52 UTC

[jira] Closed: (UIMA-574) CAS heap size is just increased by the initial heap size and is not doubled until a threshold is reached

     [ https://issues.apache.org/jira/browse/UIMA-574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Thilo Goetz closed UIMA-574.
----------------------------

       Resolution: Fixed
    Fix Version/s: 2.3

To fix this, I had to completely rework the CAS heap.  I've thrown out a lot of the ancient baggage we've still been carrying around, the file has shrunk considerably.  The page-based implementation is no more.  The changes should be mostly transparent, but I did change a couple of APIs as well.  It might be good to check that binary serialization from and to C++ still works.


> CAS heap size is just increased by the initial heap size and is not doubled until a threshold is reached
> --------------------------------------------------------------------------------------------------------
>
>                 Key: UIMA-574
>                 URL: https://issues.apache.org/jira/browse/UIMA-574
>             Project: UIMA
>          Issue Type: Bug
>          Components: Core Java Framework
>    Affects Versions: 2.3
>            Reporter: Michael Baessler
>            Assignee: Thilo Goetz
>             Fix For: 2.3
>
>
> Currently the CAS heap size is increased by the initial heap size if new heap space is required. If the initial heap space is very small there is a high performance impact for large documents.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Re: [jira] Closed: (UIMA-574) CAS heap size is just increased by the initial heap size and is not doubled until a threshold is reached

Posted by vijay vijay <vi...@gmail.com>.
Hi thilo

           can i ask u one douat?

vijay


On 9/18/07, Thilo Goetz (JIRA) <ui...@incubator.apache.org> wrote:
>
>
>     [
> https://issues.apache.org/jira/browse/UIMA-574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel]
>
> Thilo Goetz closed UIMA-574.
> ----------------------------
>
>       Resolution: Fixed
>    Fix Version/s: 2.3
>
> To fix this, I had to completely rework the CAS heap.  I've thrown out a
> lot of the ancient baggage we've still been carrying around, the file has
> shrunk considerably.  The page-based implementation is no more.  The changes
> should be mostly transparent, but I did change a couple of APIs as well.  It
> might be good to check that binary serialization from and to C++ still
> works.
>
>
> > CAS heap size is just increased by the initial heap size and is not
> doubled until a threshold is reached
> >
> --------------------------------------------------------------------------------------------------------
> >
> >                 Key: UIMA-574
> >                 URL: https://issues.apache.org/jira/browse/UIMA-574
> >             Project: UIMA
> >          Issue Type: Bug
> >          Components: Core Java Framework
> >    Affects Versions: 2.3
> >            Reporter: Michael Baessler
> >            Assignee: Thilo Goetz
> >             Fix For: 2.3
> >
> >
> > Currently the CAS heap size is increased by the initial heap size if new
> heap space is required. If the initial heap space is very small there is a
> high performance impact for large documents.
>
> --
> This message is automatically generated by JIRA.
> -
> You can reply to this email to add a comment to the issue online.
>
>