I didn't want to start a flame war, I just didn't want people being misled into thinking static vars are a big perf improvement for most code. It's better do use ordinary dynamic vars unless you're sure it will be beneficial for some tight loop somewhere. The usual case is the JIT inlines the var access and inserts a single safety-check, and many kinds of tight loops see no benefit (even when highly CPU bound).
Regarding memory barriers, I believe the JIT does the same whether the variable is volatile or not, because it can't write to memory if the inlining is invalidated. But I could be wrong. Reducing code size can also help inlining for some "inlining shapes". On Wednesday, August 6, 2014 5:54:32 AM UTC-5, Robin Heggelund Hansen wrote: > > Just read this blog post about Oxen ( > http://arrdem.com/2014/08/05/of_oxen,_carts_and_ordering/?utm_source=dlvr.it&utm_medium=twitter). > > In it is mentioned that Rich is re-introducing invokeStatic to achieve a > possible 10% performance increase for Clojure 1.7. > > I couldn't find any information about this. Anyone know where I can find > out more? > -- 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/d/optout.
