Even more constructive is to take a real Python program that you've written where you actually care about it's performance. Rewrite it Clojure. Do some investigation about which parts seem slow to you. Spend some time on this. Come back with some code and questions and you'll probably get some great answers. At that point you might start to understand what the performance characteristic of the language actually are. Perhaps some idioms in Python are faster, perhaps you need to learn new idioms to express them more efficiently in Clojure. Perhaps you'll find out some things are ungodly faster in Clojure and, of course, some things, like BigInteger math, aren't. 2009/2/3 Gregory Petrosyan <gregory.petros...@gmail.com>
> > On Feb 3, 12:50 pm, André Thieme <splendidl...@googlemail.com> wrote: > > > Hi, welcome in the group. > > Can you please write that program in Java and see how well it > > performs for you? > > Will try to compare Java and Clojure later. > > Here http://leonardo-m.livejournal.com/75825.html you can find similar > microbenchmark. Java is more than 3х slower than Python's built-in > integers, and more than 10x slower than GMPY ones. Seems like Java's > BigIntegers have some problems with performance, hm? > > > --~--~---------~--~----~------------~-------~--~----~ 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 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 -~----------~----~----~----~------~----~------~--~---
