[
http://jira.codehaus.org/browse/RVM-714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159108#action_159108 ]
David Grove commented on RVM-714:
---------------------------------
The classloading seems to be triggered by the appearance of Foo.class.getName() for most of the crypto classes.
Interestingly, all we have to do to allow class.getName to complete is to load & resolve the class (we aren't instantiating it). A sleazy trick would be to add another list of classes to the primordials which would be loaded and resolved, but not instantiated/initialized. This would reduce the work done during booting without having to handle re-running static initializers.
> Massive increase in time to execute VM.boot
> -------------------------------------------
>
> Key: RVM-714
> URL:
http://jira.codehaus.org/browse/RVM-714> Project: RVM
> Issue Type: Bug
> Reporter: Ian Rogers
> Priority: Blocker
> Fix For: svn head
>
> Attachments: verbose.out, VM.java
>
>
> r15151("Fix for RVM-700, failure for ServerSockets to work.") has caused a large amount of class loading to occur during VM.boot. This has increased the boot time by a factor of 10 on my system (0.5s to 5s).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
_______________________________________________
Jikesrvm-issues mailing list
Jikesrvm-issues@...
https://lists.sourceforge.net/lists/listinfo/jikesrvm-issues
