Mailing-List: contact open-jpa-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: open-jpa-dev@incubator.apache.org
Message-ID: <19766273.1172678217515.JavaMail.jira@brutus>
Date: Wed, 28 Feb 2007 07:56:57 -0800 (PST)
From: "Rob Wisniewski (JIRA)" <jira@apache.org>
To: open-jpa-dev@incubator.apache.org
Subject: [jira] Commented: (OPENJPA-160) Reuse BrokerImpl objects
In-Reply-To: <20132722.1172166545512.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Rob Wisniewski commented on OPENJPA-160:
----------------------------------------

Okay..  looks like the finalizer was the problem.  I took it out and we're right up where the pooling prototype puts us with respect to performance.  So the question is are we willing to take away the developer's safety net and get rid of the finalizer?  Our calculations are showing about 8% improvement for this fix alone in our particular scenario.  I like those numbers.  Is there a way we can make this work?

> Reuse BrokerImpl objects
> ------------------------
>
>                 Key: OPENJPA-160
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-160
>             Project: OpenJPA
>          Issue Type: Sub-task
>            Reporter: Michael Dick
>         Assigned To: Patrick Linskey
>         Attachments: newprofile.jpg, openjpa-160-clone-patch.txt, openjpa-160-patch.txt, openjpa-160-patch.txt, openjpa-160-patch.txt, openjpa-160-patch.txt, perf2.jpg, perf3.jpg, profile_clonepatch.jpg, profile_explicitclass.jpg
>
>


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