Thanks for your response. I attempted to answer this in my clarification, but our goal is to attack this 'general advice' and make it possible to get the same speed for array handling in natural-seeming Clojure without writing Java. In particular, we want to create macros that make it easy to achieve maximum performance by putting *your code* for manipulating array elements in the middle of an optimized loop, and this can't be done easily at the library level (as far as I can see) by dropping to Java, since in Java your code would always have to be wrapped in a method invocation with corresponding performance implications.
Our previous version of this library (developed for Clojure 1.2, IIRC) was able to get within 0-30% or so of raw Java speed while providing a clean Clojure interface, and we're trying to get back to this point with Clojure 1.5 so we can release it as open-source for everyone to use. -Jason On Friday, June 14, 2013 12:04:12 AM UTC-7, Glen Mailer wrote: > > This doesn't really answer your question directly, but is there a reason > you need to keep this in clojure, or are you just aiming to establish why > this is happening? > > My understanding was that for performance critical code the general advice > is to drop down to raw java? > > Glen > > -- -- 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.
