You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Marshall Schor (JIRA)" <de...@uima.apache.org> on 2012/05/30 17:09:23 UTC
[jira] [Closed] (UIMA-2385) Improve XmiCasDeserializer performance
[ https://issues.apache.org/jira/browse/UIMA-2385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marshall Schor closed UIMA-2385.
--------------------------------
Resolution: Fixed
Fix Version/s: 2.4.1SDK
Assignee: Marshall Schor (was: Adam Lally)
Applied patch.
> 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: Marshall Schor
> Fix For: 2.4.1SDK
>
> Attachments: UIMA-2385.bps.patch
>
>
> 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