openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Patrick Linskey (JIRA)" <j...@apache.org>
Subject [jira] Commented: (OPENJPA-439) Performance degradation in multi-transaction operations
Date Mon, 12 Nov 2007 17:57:50 GMT

    [ https://issues.apache.org/jira/browse/OPENJPA-439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12541863
] 

Patrick Linskey commented on OPENJPA-439:
-----------------------------------------

Great! Thanks for running the numbers.

> There is still one question pending. As mentioned, once all objects to be
> deleted into memory (40 mb) performing pm.deleteAll() increases the
> memory with another 45 mb. Is this as expected or should this be
> investigated as well?

I think it's definitely worth investigating. I'm going to commit the changes to this issue
and mark it as resolved, though; can you open a new issue for the potential memory leak?

> Performance degradation in multi-transaction operations
> -------------------------------------------------------
>
>                 Key: OPENJPA-439
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-439
>             Project: OpenJPA
>          Issue Type: Bug
>          Components: kernel
>    Affects Versions: 0.9.0, 0.9.6, 0.9.7, 1.0.0, 1.0.1, 1.0.2, 1.1.0
>            Reporter: Patrick Linskey
>             Fix For: 1.1.0
>
>         Attachments: OPENJPA-439-patch.jar, OPENJPA-439.patch, performance testcase results.zip,
testcaseperformance.zip
>
>
> Reusing a Broker for multiple transactions / persistence contexts demonstrates a performance
degradation, possibly due to explicit calls to clear sets and maps, rather than just dereferencing
them.
> Discussion: http://www.nabble.com/Performance-drop-in-AbstractHashedMap.clear%28%29-tf4769771.html#a13656730

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


Mime
View raw message