[
https://issues.apache.org/jira/browse/DERBY-5474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13134081#comment-13134081
]
Bryan Pendleton commented on DERBY-5474:
----------------------------------------
Wow! Years ago (2005-ish?) I did a series of experiments on a different, very
complex, build system,
to see if I could measure the impact of fork=yes vs fork=no. At that time, I
couldn't see any difference
at all; the tens of thousands of process forks that I was doing seemed to add
no time at all to the
build.
However, that was a completely different build system, a completely different
source tree, and a
completely different set of machines (principally Windows and Linux boxes on
fairly fast hardware).
So I'm pleased that you found a substantial difference, but somewhat surprised.
> Speed up message splitting in build
> -----------------------------------
>
> Key: DERBY-5474
> URL: https://issues.apache.org/jira/browse/DERBY-5474
> Project: Derby
> Issue Type: Improvement
> Components: Build tools
> Affects Versions: 10.9.0.0
> Reporter: Knut Anders Hatlen
> Assignee: Knut Anders Hatlen
> Priority: Minor
> Attachments: d5474.diff
>
>
> On a slow machine I sometimes use to build Derby, running the
> org.apache.derbyBuild.splitmessages tool takes 30 seconds and accounts for
> 15% of the total time needed to run "ant -q buildsource" (which builds the
> engine, the network server and the client, but not the tests or demos). The
> tool is invoked 15 times, and each time a new Java process is started because
> the Ant target has specified fork="yes". By changing it to run the
> splitmessages tool in the same Java process as the one running Ant, the time
> is reduced to 3-4 seconds on the same machine.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira