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)" <de...@db.apache.org> on 2006/10/16 12:23:36 UTC
[jira] Created: (DERBY-1961) Investigate resource usage for
different types of load on an in-memory database
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
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
[jira] Updated: (DERBY-1961) Investigate resource usage for
different types of load on an in-memory database
Posted by "Knut Anders Hatlen (JIRA)" <de...@db.apache.org>.
[ 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
[jira] Updated: (DERBY-1961) Investigate resource usage for
different types of load on an in-memory database
Posted by "Dag H. Wanvik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-1961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dag H. Wanvik updated DERBY-1961:
---------------------------------
Derby Categories: [Performance]
> 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
> Affects Versions: 10.2.1.6
> Reporter: Knut Anders Hatlen
> Priority: Minor
> Fix For: 10.3.1.4
>
> 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.
[jira] Closed: (DERBY-1961) Investigate resource usage for
different types of load on an in-memory database
Posted by "Knut Anders Hatlen (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (DERBY-1961) Investigate resource usage for
different types of load on an in-memory database
Posted by "Knut Anders Hatlen (JIRA)" <ji...@apache.org>.
[ 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
[jira] Updated: (DERBY-1961) Investigate resource usage for
different types of load on an in-memory database
Posted by "Knut Anders Hatlen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-1961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Knut Anders Hatlen updated DERBY-1961:
--------------------------------------
Affects Version/s: 10.2.1.6
Derby 10.2.1.6 was used in the tests.
> 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
> 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.
[jira] Commented: (DERBY-1961) Investigate resource usage for
different types of load on an in-memory database
Posted by "Knut Anders Hatlen (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1961?page=comments#action_12442566 ]
Knut Anders Hatlen commented on DERBY-1961:
-------------------------------------------
Created wiki page where results could be posted: http://wiki.apache.org/db-derby/Derby1961ResourceUsage
> 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