You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 29, 2018. It is now read-only.
If we can uncompress jbosseap jar files, it would save 20% of CPU usage spent for uncompressing jar files at runtime and get jbosseap boot process faster. This trick is used in Java itself - the core api rt.jar is an uncompress jar.
On my laptop, using standard compressed jars:
13:49:38,660 INFO [org.jboss.as](Controller Boot Thread) JBAS015874: JBoss EAP 6.3.0.GA (AS 7.4.0.Final-redhat-19) started in 3130ms - Started 151 of 189 services (56 services are lazy, passive or on-demand)
Using EAP uncompressed jars:
13:52:50,581 INFO [org.jboss.as](Controller Boot Thread) JBAS015874: JBoss EAP 6.3.0.GA (AS 7.4.0.Final-redhat-19) started in 2631ms - Started 151 of 189 services (56 services are lazy, passive or on-demand)
The jbosseap jars are installed via rpm, so we probably need a tricky approach to implement this:
Release uncompress version of jbosseap rpm
Hook and generate uncompress version
jbosseap cartridge generates uncompress version of jbosseap from jbosseap rpm
Other?
What do you think?
The text was updated successfully, but these errors were encountered:
If we can uncompress jbosseap jar files, it would save 20% of CPU usage spent for uncompressing jar files at runtime and get jbosseap boot process faster. This trick is used in Java itself - the core api rt.jar is an uncompress jar.
On my laptop, using standard compressed jars:
Using EAP uncompressed jars:
The jbosseap jars are installed via rpm, so we probably need a tricky approach to implement this:
What do you think?
The text was updated successfully, but these errors were encountered: