[ 
https://issues.apache.org/jira/browse/BUILDR-658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13764454#comment-13764454
 ] 

Tammo van Lessen commented on BUILDR-658:
-----------------------------------------

This is a great idea. If I understand correctly, this would render the 
all-in-one-package into a all-in-one-jarfile, right? This could also 
significantly lower the burden for new users since projects could ship with a 
mechanism (similar to gradle's) that provides a very slim code to download the 
all-in-one-package into an ignored folder and then launch buildr from there.
                
> Improve the speed of the all-in-one package
> -------------------------------------------
>
>                 Key: BUILDR-658
>                 URL: https://issues.apache.org/jira/browse/BUILDR-658
>             Project: Buildr
>          Issue Type: Bug
>          Components: Packaging
>    Affects Versions: 1.4.10
>            Reporter: Peter Donald
>            Assignee: Peter Donald
>             Fix For: 1.4.13
>
>
> Running buildr under jruby is slow. A large portion of the blame can be 
> attributed to rubygems and some can be attributed  to the startup time of 
> parsing the ruby files and the bytecode compilation under the JVM.
> It seems this is largely fixable by applying a few ugly hacks. These include;
> * Extracting all the ruby code into one directory. (Seems to show the biggest 
> improvement)
> * Running jrubyc over the codebase and replacing all the .rb files with 
> quires against the .class files such as warbler does
> In one project we applied these techniques and our startup time when from 
> ~23s to ~1.5s however some projects see even better improvements. See [1] for 
> a better explanation and some additional tricks to try.
> [1] 
> https://logstash.jira.com/browse/LOGSTASH-563?focusedCommentId=14695&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14695

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to