That is the only set of changes that I know of that negatively affect performance in 1.6.0. However, the absolute differences are quite small and codes are cached. It's hard for me to conjure a scenario where the resulting effect is an overall 5-8% slowdown. If this is one, I'd like to understand it better.
On Wednesday, March 19, 2014 8:28:18 AM UTC-5, Nicola Mometto wrote: > > > I'm guessing it's because of the minor overhead on hashing added with > the move to Murmur3? > > Alex Miller writes: > > > <record scratch> what's that about performance now? > > > > Is that something definitive and reproducible? And if so, is there any > way to track down a cause? > -- 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.
