Hi Andy: Thanks a lot for your reply. I'll do more careful testing in the very near future and there is surely a lot to optimize in my code. I must say I did expect computing speed reduction coming from an already optimized codebase with the perfomance critical parts written in C, and there is an intentional trade off in my porting effort to get something more maintainable, extensible and scalable. My future plans are to run in a cluster on something like EC2, because I've made the numbers and buying hardware isn't cost effective for us anymore (we paid around EUR 10K for our last big computer and we can do a lot of computing in the cloud for that money). Since the software is used for research, we tend to add features and change it so that it simulates the different scenarios coming out of our scientific discussions: This means we spend almost as much time coding as simulating, and having a higher level language like Clojure helps us enormously.
I'll keep you posted about my future performance tests and the Open Source release of the software. Best, Jose. -- -- 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.
