This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2015-09-07
Channels
- # beginners (7)
- # boot (25)
- # clojure (66)
- # clojure-australia (10)
- # clojure-berlin (1)
- # clojure-czech (1)
- # clojure-denmark (2)
- # clojure-france (27)
- # clojure-italy (6)
- # clojure-japan (1)
- # clojure-nl (5)
- # clojure-norway (1)
- # clojure-russia (25)
- # clojurescript (55)
- # cursive (27)
- # datascript (2)
- # datomic (5)
- # editors (4)
- # emacs (2)
- # hoplon (183)
- # ldnclj (45)
- # off-topic (4)
- # om (2)
- # rdf (5)
- # re-frame (11)
- # reagent (5)
- # ring (3)
I’m doing some performance testing of my Clojure app, and it seems the bare minimum will happily eat 350MB of RAM (Jetty with 6 threads, the minimum). As soon as I add Nashorn, it jumps to >512MB. Is this common or am I experience a problem here? Clojure/Java being memory hungry might have an effect on whether I use Heroku or not.
måning
@pupeno: ime the jvm isn't super fast/happy until it has ~3gb of ram. Not surprised you have issues on Heroku
I just published what I think it’s the most comprehensive blog post in how to use New Relic with Clojure: https://carouselapps.com/2015/09/07/using-new-relic-with-clojure/
For a few more experiments I think I’ll use big heroku instances for now for some experiments but then I’ll move to VPSs.
I do know capistrano as I use it already. Using bash would mean having to build a lot of plumbing that capistrano does for me.
fair enough then It depends how complex your deploys are. Yeller's deploy system doesn't keep around old deploy artifacts or anything like that, just shoves a file in a place and kills the existing process
Also, are people just deploying uberjars that run standalone? No container like Tomcat? I’m new to the Java world so I don’t know if it’s a good idea to just run the uberjar.
tcrayford: thanks for pointing it about 3GB of ram. I’m running with 1GB and I can’t go above 0.9 hits per second.