You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@buildr.apache.org by "Peter Donald (JIRA)" <ji...@apache.org> on 2014/08/25 23:08:59 UTC

[jira] [Updated] (BUILDR-658) Improve the speed of the all-in-one package

     [ https://issues.apache.org/jira/browse/BUILDR-658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Peter Donald updated BUILDR-658:
--------------------------------

    Fix Version/s:     (was: 1.4.19)
                   1.4.20

> 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.20
>
>
> 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 was sent by Atlassian JIRA
(v6.2#6252)