Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <28731144.1181856626466.JavaMail.jira@brutus>
Date: Thu, 14 Jun 2007 14:30:26 -0700 (PDT)
From: "Knut Anders Hatlen (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Closed: (DERBY-1961) Investigate resource usage for
 different types of load on an in-memory database
In-Reply-To: <23558605.1160994216371.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-1961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Knut Anders Hatlen closed DERBY-1961.
-------------------------------------

       Resolution: Fixed
    Fix Version/s: 10.3.0.0

The investigation has been completed and the results are available on the wiki. Thanks to Dyre and Kristian for contributing data.

> Investigate resource usage for different types of load on an in-memory database
> -------------------------------------------------------------------------------
>
>                 Key: DERBY-1961
>                 URL: https://issues.apache.org/jira/browse/DERBY-1961
>             Project: Derby
>          Issue Type: Task
>          Components: Performance
>    Affects Versions: 10.2.1.6
>            Reporter: Knut Anders Hatlen
>            Priority: Minor
>             Fix For: 10.3.0.0
>
>         Attachments: TestClient.java
>
>
> Investigate how much resources Derby uses and in which parts of the
> code they are used on an in-memory database. Find numbers for
> different kinds of load: single-record update and select operations,
> and join operations.
> Example of resource usage that could be measured: CPU, wall-clock
> time, system calls, context switches, monitor contention, object
> allocations, garbage collection, I/O.

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