uima-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Adam Lally (JIRA)" <...@uima.apache.org>
Subject [jira] [Commented] (UIMA-2385) Improve XmiCasDeserializer performance
Date Mon, 14 May 2012 15:17:53 GMT

    [ https://issues.apache.org/jira/browse/UIMA-2385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13274670#comment-13274670

Adam Lally commented on UIMA-2385:

I consider this analogous to how an ArrayList's capacity grows in Java.  They provided some
reasonable implementation that seems to work for everyone, and they don't expose ways to tune

With the multi limit at 512K we are talking about at most 4MB of unused space, and I don't
consider that excessive.  As I said though, I wouldn't object if someone made this parameterizable.
> Improve XmiCasDeserializer performance
> --------------------------------------
>                 Key: UIMA-2385
>                 URL: https://issues.apache.org/jira/browse/UIMA-2385
>             Project: UIMA
>          Issue Type: Improvement
>          Components: Core Java Framework
>    Affects Versions: 2.4.0SDK
>            Reporter: Adam Lally
>            Assignee: Adam Lally
> I profiled an expensive CAS deserialization and found that 46% of the time was in CASImpl.ll_getFSForRef
(the method that creates a FeatureStructure Java object for a CAS FS).  All those calls were
coming from deserializing arrays (of which this particular CAS has many).
> It is unnecessary to create FeatureStructure Java objects here.  For non-array FSs, XmiCasDeserializer
uses low-level CAS APIs in order to avoid this overhead.  But for arrays, it currently does
not use the low-level APIs.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message