harmony-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Harmony Wiki] Update of "Startup Performance" by AlexeiFedotov
Date Mon, 04 Feb 2008 14:37:11 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Harmony Wiki" for change notification.

The following page has been changed by AlexeiFedotov:
http://wiki.apache.org/harmony/Startup_Performance

New page:
== Startup Performance Measurement ==
   1. The first startup
   1. A subsequent startup of the same application
   1. A subsequent startup of a different application

== Applications ==
   * Eclipse startup is known for bothering users. A subsequent eclipse startups should be
improved.
   * SpecJVM2008 includes startup measurements into final score. It seems that subsequent
runs would help improving peek score.

== Ideas ==
   * Use pools mapped to files to speed up loading of classes from the boot class path. Alexei
Shipilev knows well dll memory layout to make mapping at the same virtual address work.
   * Precompile / save jitted code for later use.
   * Store compiled code in DLL/SO formats. Do not reinvent formats for code. If VM has a
compiler, why should not it have a linker?
   * Use single boot class path cache.
   * Read jar files by means of memory mapping.
   * Think of unpacking jar files, make the size of unpacked jars reasonable (see investigate
Natalia’s JIRA.
     * Remove debugging information from class files.
     * Obfuscate private and undocumented class fields.
   * Reorder boot class path putting important jars first.
   * Save VM state dumping heap memory, thread stacks, states of files, sockets and other
open resources. While the task look heavy, for a particular application use case this might
be doable.

(Thanks Pavel Pervov, Alexei Shipilev, Eugenia Maenkova, Andrey Yakushev, Sergey Kuksenko)

Mime
View raw message