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 "Daniel John Debrunner (JIRA)" <ji...@apache.org> on 2007/07/05 23:34:04 UTC
[jira] Created: (DERBY-2904) Investigate the performance effect of
adding an index to the Derby jar files (derby.jar, etc.)
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
Components: Performance
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.
[jira] Commented: (DERBY-2904) Investigate the performance effect
of adding an index to the Derby jar files (derby.jar, etc.)
Posted by "Daniel John Debrunner (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12510912 ]
Daniel John Debrunner commented on DERBY-2904:
----------------------------------------------
Yes, it can easily enabled using ant's jar target.
> 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
> Components: Performance
> 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.
[jira] Commented: (DERBY-2904) Investigate the performance effect
of adding an index to the Derby jar files (derby.jar, etc.)
Posted by "Bryan Pendleton (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12510909 ]
Bryan Pendleton commented on DERBY-2904:
----------------------------------------
Hi Dan, is this the feature you're referring to?
http://java.sun.com/j2se/1.3/docs/guide/jar/jar.html#JAR%20Index
> 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
> Components: Performance
> 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.
[jira] Updated: (DERBY-2904) Investigate the performance effect of
adding an index to the Derby jar files (derby.jar, etc.)
Posted by "Dag H. Wanvik (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (DERBY-2904) Investigate the performance effect of
adding an index to the Derby jar files (derby.jar, etc.)
Posted by "Dag H. Wanvik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dag H. Wanvik updated DERBY-2904:
---------------------------------
Component/s: Miscellaneous
> 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
> Components: Miscellaneous
> 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.