Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <14955007.1192138852356.JavaMail.jira@brutus>
Date: Thu, 11 Oct 2007 14:40:52 -0700 (PDT)
From: "Knut Anders Hatlen (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Closed: (DERBY-3004) Get rid of the finalizer in
 EmbedResultSet
In-Reply-To: <12831955.1187077532418.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/DERBY-3004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Knut Anders Hatlen closed DERBY-3004.
-------------------------------------


> Get rid of the finalizer in EmbedResultSet
> ------------------------------------------
>
>                 Key: DERBY-3004
>                 URL: https://issues.apache.org/jira/browse/DERBY-3004
>             Project: Derby
>          Issue Type: Improvement
>          Components: JDBC, Performance
>    Affects Versions: 10.3.1.4
>            Reporter: Knut Anders Hatlen
>            Assignee: Knut Anders Hatlen
>            Priority: Minor
>             Fix For: 10.4.0.0
>
>         Attachments: d3004.diff, d3004.stat
>
>
> Finalizers make object allocation and garbage collection more expensive and should be avoided for object types that are frequently allocated. EmbedResultSet has a finalize() method and is frequently allocated for many types of load. The following comment was posted on DERBY-1876:
> By commenting out the finalize() method in EmbedResultSet, the time to run the test on my laptop is reduced from ~3 seconds to ~1.3 seconds (OpenSolaris, Sun Java SE 6). Since the finalizer is a no-op if the activation isn't single-use, I think we should investigate whether there are ways to avoid this cost for ResultSets that don't need the finalizer.

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