[ https://issues.apache.org/jira/browse/HARMONY-6039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12663736#action_12663736
]
Pavel Pervov commented on HARMONY-6039:
---------------------------------------
You can be unable to write to either DRLVM or class library tree due to security restrictions
in file system.
> Implement on-demand class library parsing to avoid unnecessary jar/zip parsing during
startup
> ---------------------------------------------------------------------------------------------
>
> Key: HARMONY-6039
> URL: https://issues.apache.org/jira/browse/HARMONY-6039
> Project: Harmony
> Issue Type: Improvement
> Components: VM
> Environment: Conduct experiments on Windows XP, Core 2 Quad-core machine
> Reporter: Wenlong Li
> Assignee: Xiao-Feng Li
> Attachments: h6039.patch_1, H6039.patch_2, H6039_on_demand_library_parsing_patch,
instrumentation_code, On-demand runtime library loading_1, On-demand runtime library loading_2,
on_demand_patch
>
>
> During VM creation, Harmony will parse all class libraried defined in bootclasspath.properties
under jre/lib/boot directory. However, not all class libraries are accessed during startup.
That means, it is not necessary to open and resolve all these class libraries.
> In this patch, I implement the on-demand jar parsing. I leverage the class library info
defined in the manifest file of each module. For a request class, if it is not available in
existing class table, I then parse its class library info, and check which module contains
this requested class. That is, I parse the class library on demand.
> Using on-demand class library parsing, I can reduce the VM creation time from 20+ seconds
to 3 seconds.
> I enable this feature into reading boot class path option, and it can be disabled by
using -Xbootclasspath option.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.