You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Knut Anders Hatlen (JIRA)" <ji...@apache.org> on 2006/11/02 14:33:19 UTC

[jira] Commented: (DERBY-1961) Investigate resource usage for different types of load on an in-memory database

    [ http://issues.apache.org/jira/browse/DERBY-1961?page=comments#action_12446601 ] 
            
Knut Anders Hatlen commented on DERBY-1961:
-------------------------------------------

The wiki page disappeared and I was unable to restore it with the same name. New location for the results: http://wiki.apache.org/db-derby/Derby1961ResourceUsage2

> Investigate resource usage for different types of load on an in-memory database
> -------------------------------------------------------------------------------
>
>                 Key: DERBY-1961
>                 URL: http://issues.apache.org/jira/browse/DERBY-1961
>             Project: Derby
>          Issue Type: Task
>          Components: Performance
>            Reporter: Knut Anders Hatlen
>            Priority: Minor
>         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.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira