I've changed it to allow variable board sizes. Finding it difficult to profile Clojure code though for performance tuning. Using the -Xprof switch seems to indicate java.lang.Character.hashCode is called a lot and i guess that's to do with the nested maps that represent the trie.
Using jvisualvm doesn't help much either as it's not giving me a call graph. Just self counts for each function, so it's difficult to see how it related to the clojure code. On Nov 7, 7:11 pm, james <ja...@3dengineer.com> wrote: > Hey! > > As a learning exercise I wrote a simplebogglesolver in clojure. > I'm sure there is lots of room for improvement to make it more > idiomatic and perform better so I would be grateful if anyone would > care to cast their eye over it. > > http://wiki.github.com/phraemer/Boggle-Solver > > thanks, > > James -- 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
