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 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 in your project. Solutions: a) Don't require all your namespaces immediately. Get your app/GUI running first, then require all the other stuff on demand / when it is needed. This massively improves *perceived* startup time. b) Use a persistent REPL for development purposes. You shouldn't need to restart it all the time. On Thursday, 30 January 2014 05:44:45 UTC+8, 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 performance during development. > -- -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
