uima-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Richard Eckart de Castilho (JIRA)" <...@uima.apache.org>
Subject [jira] [Comment Edited] (UIMA-5801) Performance degradation of jCas.reset when repeatedly used in different analysisEngines
Date Wed, 04 Jul 2018 05:33:00 GMT

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

Richard Eckart de Castilho edited comment on UIMA-5801 at 7/4/18 5:32 AM:
--------------------------------------------------------------------------

So uimaFIT and probably other pipeline runners like CPE or UIMA-AS now need to be changed
an call `destroy()` on the RMs they create, right?


was (Author: rec):
So uimaFIT and probably other pipeline runners like CPE or UIMA-AS now need to be changed
an call `close()` on the RMs they create, right?

Btw. I think the initial discussion on cleaning up resources from a RM was not about calling
`close()` (which does not exist in current code) but about calling `destroy()` which does
exist in current code but is never called.

> Performance degradation of jCas.reset when repeatedly used in different analysisEngines
> ---------------------------------------------------------------------------------------
>
>                 Key: UIMA-5801
>                 URL: https://issues.apache.org/jira/browse/UIMA-5801
>             Project: UIMA
>          Issue Type: Bug
>          Components: UIMA
>    Affects Versions: 2.1
>            Reporter: David Bürkle
>            Assignee: Marshall Schor
>            Priority: Major
>         Attachments: JCasPerformanceTest.java
>
>
> The execution time of jCas.reset() increases linearly when invoked on the same jCas.
> This occurs in a loop that builds a new analysisEngine, processes the jCas and resets
it.
> This does not occur when the same analysisEngine is reused.
> A junit test demonstrating the behaviour is attatched.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message