Improving startup time of Clojure REPL with Leiningen on the Raspberry Pi

Question

I got a Rasperry Pi 512 MB version (late 2012) and installed the Developer Preview of Java SE 8 for ARM on it. When I create a new Clojure project with Leiningen and launch the nREPL by doing lein repl it takes a bit more than two minutes (roughly 130 - 140 seconds) until the REPL has been initialized and can be used.

When launching the JAR file directly java -jar clojure-1.4.0/clojure-1.4.0 the REPL starts up in 25s.

I'm using fast class 10 SD cards (SanDisk Extreme with up to 30 MB/s). How come that the difference between using Leiningen with nRepl vs launching the JAR file is so big? What could be done to improve the startup time with Leiningen for the Raspberry Pi?

`lein repl` checks dependencies, builds the project and prepares auto completion and other shenanigans like that. You could try to do clever things like keeping a JVM with Clojure loaded to run leiningen on around, but I'm not sure how much that would actually reduce the startup time. I suppose ideally, you should just try to not run `lein repl` very often. — Cubic, Dec 26 '12 at 12:06
Yes, that's what I've been thinking as well. I've seen similar discussions on the Clojure mailing list, but on a desktop PC or notebook the slowdown is not as bad as it is on the Raspberry Pi. Common Lisp REPL starts up in 1s, the performance overhead for Java and classpath scanning is pretty heavy. Not sure if Clojure is such a good development platform for embedded devices. — raju-bitter, Dec 26 '12 at 15:10
raju-bitter, I'm curious of what Common-Lisp implementation are you using in the Pi... — Diego Sevilla, Dec 27 '12 at 01:09
GNU CLISP 2.49 (2010-07-07), it's in the repository for Wheezy. Just did a `sudo apt-get install clisp`. — raju-bitter, Dec 27 '12 at 08:58
This seems to explain some of it http://nicholaskariniemi.github.io/2014/02/25/clojure-bootstrapping.html — Adam Gent, Dec 10 '14 at 12:48
See also http://dev.clojure.org/display/design/Improving+Clojure+Start+Time — Vadzim, Sep 23 '16 at 20:46

score 2 · Answer 1 · answered Nov 13 '13 at 23:37

2

Also try grenchman: Fast invocation of Clojure code over nREPL.

answered Nov 13 '13 at 23:37

Daniel Szmulewicz

3,971
2
25
26

score 1 · Answer 2 · answered Jan 08 '13 at 22:40

1

You can try drip which wraps the java command and prepare a fresh jvm waiting in the background.

answered Jan 08 '13 at 22:40

ordnungswidrig

3,140
1
18
29

Thanks, I'll try that and report the results here. – raju-bitter Jan 09 '13 at 12:03

score 1 · Answer 3 · edited Sep 23 '16 at 20:36

1

It seems the slow startup of clojure in general is the loading of core and various other things discussed here:

http://blog.ndk.io/solving-clojure-boot-time.html

edited Sep 23 '16 at 20:36

Vadzim

24,954
11
143
151

answered Dec 10 '14 at 12:53

Adam Gent

47,843
23
153
203

score 0 · Answer 4 · answered Dec 10 '14 at 12:02

Actually the Leiningen starts in it's own JVM and then nests the project's vm inside it.
Then it checks deps, figures out the changes and so on.

You can avoid vm nesting with the trampoline task of lein like so:
lein trampoline repl

But this command requires the lein to be called in a project directory

Improving startup time of Clojure REPL with Leiningen on the Raspberry Pi

4 Answers4

Linked