On Jan 29, 2014, at 6:58 PM, Mikera wrote:
> The real issue issue is loading / initialisation of Clojure code after JVM
> startup - i.e. loading clojure.core and the (potentially large) graph of
> required namespaces. This quickly becomes noticeable if you are using a large
> set of libraries
The JVM startup time usually *isn't* the problem. I've benchmarked my JVM
starting up and running a simple "hello world" app in less than 0.1secs.
java version "1.7.0_51"
Java(TM) SE Runtime Environment (build 1.7.0_51-b13)
Java HotSpot(TM) 64-Bit Server VM (build 24.51-b03, mixed mode)
The real
On Jan 29, 2014, at 1:44 PM, ton...@gmail.com wrote:
> Are there any Java VMs strictly for development use that could be started up
> quicker, use less memory or compile clojure during execution? Alternatively
> can OpenJDK or similar be configured to do so? I don't care about application
> pe
my vm starts up within a second or so, what's the problem for you?
2014-01-29
> Are there any Java VMs strictly for development use that could be started
> up quicker, use less memory or compile clojure during execution?
> Alternatively can OpenJDK or similar be configured to do so? I don't car
Are there any Java VMs strictly for development use that could be started
up quicker, use less memory or compile clojure during execution?
Alternatively can OpenJDK or similar be configured to do so? I don't care
about application performance during development.
--
--
You received this messag
