This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-06-14
Channels
- # aws (6)
- # babashka (31)
- # beginners (69)
- # biff (9)
- # boot (9)
- # bristol-clojurians (1)
- # calva (20)
- # chlorine-clover (2)
- # cider (8)
- # cljsrn (24)
- # clojure (25)
- # clojure-norway (4)
- # clojure-spec (29)
- # clojure-uk (7)
- # conjure (23)
- # datahike (5)
- # datomic (39)
- # emacs (4)
- # fulcro (4)
- # graalvm (11)
- # honeysql (1)
- # lambdaisland (1)
- # leiningen (8)
- # liberator (1)
- # libpython-clj (3)
- # malli (6)
- # mxnet (1)
- # off-topic (94)
- # pedestal (13)
- # re-frame (4)
- # releases (2)
- # shadow-cljs (8)
- # spacemacs (22)
- # sql (9)
- # vim (1)
When boot build target -d target
is several times slower than "normal"/expected on macOS, what's the most common things people investigate? Does having 10GB test data in project directory impact something like that? I'm taking a simple measurement of build time now, but it's several minutes, whereas 15 seconds to complete. I'm obviously doing something wrong 🙂lein uberjar
took
$ /usr/bin/time boot build target -d target
Compiling 1/1 test-proj.core...
Writing pom.xml and pom.properties...
Adding uberjar entries...
Writing test-proj-0.1.0.jar...
Writing target dir(s)...
1632.47 real 40.66 user 364.85 sys
$ lein clean && /usr/bin/time lein uberjar
OpenJDK 64-Bit Server VM warning: Options -Xverify:none and -noverify were deprecated in JDK 13 and will likely be removed in a future release.
OpenJDK 64-Bit Server VM warning: Options -Xverify:none and -noverify were deprecated in JDK 13 and will likely be removed in a future release.
Compiling test-proj.core
Created /<redacted path>/test-proj/target/uberjar/test-proj-0.1.0-SNAPSHOT.jar
Created /<redacted path>/test-proj/target/uberjar/test-proj-0.1.0-SNAPSHOT-standalone.jar
15.32 real 27.59 user 5.09 sys
10GB in your project? OMG that would probably murder the hard drive, boot tasks copy the project dir to their own temp folder, this could result in huge hard drive usage
you should probably break up the project into smaller modules
unless the test data is something like a database, then you just need to filter the fileset to remove it
Thanks, but I tested this without having the test data in the project base dir.
Additionally, target dir is ~23 MB so I don't think it's copying those 10GB test data.
Unless it's copying and discarding of course. This is on nvme drives, so it takes ~20s to copy that data.