Fork me on GitHub
#leiningen
<
2019-04-13
>
michaeljameserwin03:04:47

Having an issue where lein run is taking me 3m30s and taking my coworkers only 30s

michaeljameserwin03:04:33

Every chance at parity has been attempted. I actually have a newer/faster system than anyone else

michaeljameserwin03:04:03

It mostly seems to hang at what I'd call namespace collisions (.e.g WARNING: name already refers to: #'clojure.core/name in namespace:...), at least that's what's printing while it takes the longest, which I'd guess is during compile

jumar07:04:43

could it be that you have many plugins/dependencies in your .lein/profiles.clj?

alexmiller11:04:56

Any chance you’re using user.clj and latest jdk (8u202+ or 11.0.2)?

alexmiller11:04:30

There is a known Java perf regression with these that has a dramatic impact when loading user.clj

alexmiller11:04:18

Clojure 1.10.1-beta2 has a mitigation fix in it we are testing

michaeljameserwin14:04:49

.lein/profiles.clj just has env vars basically.

michaeljameserwin14:04:10

@alexmiller let me take a look at jdk version, that might be it

michaeljameserwin14:04:29

we are using a user.clj

michaeljameserwin14:04:23

Looks like I'm on java 8u201 though:

$ java -version
java version "1.8.0_201"
Java(TM) SE Runtime Environment (build 1.8.0_201-b09)

michaeljameserwin15:04:28

So I downgraded my jdk to 8u192 and it fixed my build time

alexmiller23:04:32

Sorry 8u201 was bad too

alexmiller23:04:50

I’d say it’s almost certain that’s it