-
Notifications
You must be signed in to change notification settings - Fork 99
High memory consumption #49
Comments
Hi, thanks for reporting! The three processes are leiningen, the repl, and figwheel. You can bring it down to two by using Unfortunately Figwheel can't be used as a library, which means we have to invoke it through leiningen, so that creates an extra JVM. See also #47. Apart from that this behavior is indeed "normal", although 2GB seems like a lot. For me it's more around 500MB. There are various flags to control or limit the amount of memory the JVM uses, you could experiment with those. |
Would you be willing to share some details about your setup? I'm having a hard time understanding why someone people have such low memory numbers... |
This is what I use
Not much special for the rest. Is it only with chestnut projects that you have this? Maybe compare with some other configs to see what part is so memory hungry. So do a |
Thank you for your help! I have upgraded to JDK 1.8 and now my setup matches what you described (apart from the OS, of course). A couple of notes:
Yes, I have noticed this with other projects as well but this case was unfortunately especially bad. Thanks again. |
Glad it's better now. It's good to know this is a pain point. I hope we can make it all work seemlessly in a single process eventually. |
I've been watching this and been thinking a lot about making a library thats executable from the repl. |
I think lively could be embedded in the process easily. You'd need to handle Clojurescript compilation on your own then though. |
@bhauman that would be absolutely fabulous! @martinklepsch how does lively relate to figwheel? Are they completely separate implementations? |
@plexus They're separate. Lively only implements the pushing of new code to the the browser. And does not care about compiling Clojurescript. |
Just want to let you know that I just released lein-figwheel 0.2.0-SNAPSHOT and you can now launch the autobuilder/change server from the new figwheel-sidecar library. Unfortunately config options are not yet validated at this level. The config validation is all still up in the leiningen plugin. |
Thank you @bhauman , that's great news! |
I created the default project with
lein new chestnut <xyz>
, started the repl withlein repl
followed by(run)
and(browser-repl)
. Before doing this, I removed all of my plugins from~/.lein/profiles.clj
.I am now left with 3 java processes. Together, these processes use almost 2GB of memory.
This is on OSX 10.10 and here is the repl session if it helps.
Is this normal? Can something be done about this?
The text was updated successfully, but these errors were encountered: