db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dag H. Wanvik (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-2904) Investigate the performance effect of adding an index to the Derby jar files (derby.jar, etc.)
Date Mon, 29 Jun 2009 14:07:47 GMT

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

Dag H. Wanvik updated DERBY-2904:
---------------------------------

    Derby Categories: [Performance]

> Investigate the performance effect of adding an index to the Derby jar files (derby.jar,
etc.)
> ----------------------------------------------------------------------------------------------
>
>                 Key: DERBY-2904
>                 URL: https://issues.apache.org/jira/browse/DERBY-2904
>             Project: Derby
>          Issue Type: Improvement
>            Reporter: Daniel John Debrunner
>            Priority: Minor
>
> Since JDK 1.3 the Java jar format has supported an index to speed up class loading. Sounds
like it would be useful for derby's jar file, especially derby.jar with its many classes.
The ant jar target has an index attribute to enabled the index.
> Would be interesting to see the performance benefit and the increased size of the jar
files.
> As a thought for a performance test, a simple test that loaded Derby in separate class
loaders, opened an existing database and executed a query to load as many classes as possible.
>  for (number of iterations)
>  {
>     create new class loader
>     load derby in class loader
>     boot database
>     prepare query
>     shutdown derby
> }
> Then time with a reasonable number of iterations. (I think 1 is too few, hence the use
of a class loader).

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


Mime
View raw message