db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <derby-...@db.apache.org>
Subject [jira] Updated: (DERBY-1961) Investigate resource usage for different types of load on an in-memory database
Date Mon, 16 Oct 2006 10:31:35 GMT
     [ http://issues.apache.org/jira/browse/DERBY-1961?page=all ]

Knut Anders Hatlen updated DERBY-1961:

    Attachment: TestClient.java

Uploaded a test client which can be used to investigate the resource
usage for three different loads:

  - single-record select operations: select one row from a table of
    100000 rows (each row is 100 bytes)

  - single-record update operations: update one row in a table of
    100000 rows (same table as above)

  - join of a table of 10000 rows with a table of 1000 rows - 1000
    rows in each result

All operations use primary keys. The joins work on tables which have
the same schema as the tables in the Wisconsin test in Derby's
regression test suite. The client uses the Wisconsin test code to fill
the tables, and therefore derbyTesting.jar must be in the classpath
when the test database is initialized. Run "java TestClient -h" to
learn how to run the test clients.

> 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


View raw message