Open barbeau opened 7 years ago
For speeding up NPM installs, see https://lincolnloop.com/blog/speeding-npm-installs/.
For caching with frontend-maven-plugin see discussion at https://github.com/eirslett/frontend-maven-plugin/issues/27, and potential solution at https://github.com/eirslett/frontend-maven-plugin/pull/118.
I tried the solution at https://github.com/eirslett/frontend-maven-plugin/pull/118, but it didn't seem to have any effect - I didn't see any new cache
directory. I bumped the version of frontend-maven-plugin in https://github.com/CUTR-at-USF/gtfs-realtime-validator/commit/0d0f3811bcedae16320739b2645f23595ce02c94 just so we inherit any improvements there.
Running mvn -T 4 install
to increase number of threads doesn't seem to have any speed up effect either.
Summary:
mvn package
can take a while to execute - most of this time is due to pulling the components needed to build gtfs-validator-webapp (https://github.com/conveyal/gtfs-validator/tree/master/gtfs-validator-webapp) so we can display the results in our webapp.We should try to speed this up. We are using https://github.com/eirslett/frontend-maven-plugin to build the webapp via npm and gulp + browserfy.
Possible options for speedup:
<phase>
ascompile
, but the default according to https://github.com/eirslett/frontend-maven-plugin#usage the default<phase>
isgenerate-resources
. Would changing togenerate-resources
speed up the build?Steps to reproduce:
Execute
mvn package
Expected behavior:
Build fairly quickly
Observed behavior:
Builds take a while to complete - around 3 min 16 sec for
mvn clean package
, and about 2 min 9 sec formvn package
after that initial build on my dual CPU Xeon @ 2.5 GHz and 16 GB of RAM.