[
https://issues.apache.org/jira/browse/DERBY-5474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13134827#comment-13134827
]
Knut Anders Hatlen commented on DERBY-5474:
-------------------------------------------
I didn't have any JAVA_OPTS or ANT_OPTS set. All the machines I tested on had 4
GB of RAM, which should be sufficient to build Derby, I think.
The next problem I found, was that the <chmod> tasks in the binscripts target
need close to half a second on all the platforms I have tested (Solaris and
Linux). There are six of those, so it totals to three seconds, also in
incremental builds when there shouldn't be anything to do. I'll file a separate
issue for that. I don't understand this either. Executing six chmod commands
from a shell script takes a few milliseconds, so I don't see why doing the same
from Ant should take three seconds. Oh well...
For the record, I timed the targets by running Ant with these extra parameters:
-logger org.apache.tools.ant.listener.ProfileLogger
> 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
> Fix For: 10.9.0.0
>
> 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
