Re: Clojure for Scientific and other CPU-intensive Computing

2009-07-01 Thread Daniel E. Renfer
Mark Engelberg mark.engelb...@gmail.com writes: On Tue, Jun 30, 2009 at 12:29 AM, Konrad Hinsenkonrad.hin...@laposte.net wrote: What is particularly nice about Clojure is that in most situations you don't need to switch to Java for speed. You can optimize your code by adding type hints and

Re: Clojure for Scientific and other CPU-intensive Computing

2009-07-01 Thread Konrad Hinsen
On Jun 30, 2009, at 19:07, Mark Engelberg wrote: On Tue, Jun 30, 2009 at 12:29 AM, Konrad Hinsenkonrad.hin...@laposte.net wrote: What is particularly nice about Clojure is that in most situations you don't need to switch to Java for speed. You can optimize your code by adding type hints and

Re: Clojure for Scientific and other CPU-intensive Computing

2009-06-30 Thread kyle smith
On Jun 30, 2:41 am, fft1976 fft1...@gmail.com wrote: I would be curious to know if anyone is using Clojure for CPU- intensive work where performance really counts. I'm using clojure for various computational physics tasks: 1. I'm writing a dsl for substructure searching. 2. I'm doing classical

Re: Clojure for Scientific and other CPU-intensive Computing

2009-06-30 Thread Konrad Hinsen
On 29.06.2009, at 20:41, fft1976 wrote: It's been argued by some that Clojure is as fast as Java, because at worst, you can implement your bottlenecks in Java. I have a problem with this argument, because the data structures that your Java has to work with are still (wasteful) Clojure ones.

Re: Clojure for Scientific and other CPU-intensive Computing

2009-06-30 Thread Daniel Lyons
On Jun 29, 2009, at 12:41 PM, fft1976 wrote: Based on the recent survey What are people using Clojure for?, people are mostly using it for non-CPU-intensive work, like parsing, report generation, GUIs, glue code. It's been argued by some that Clojure is as fast as Java, because at worst,

Re: Clojure for Scientific and other CPU-intensive Computing

2009-06-30 Thread fft1976
On Jun 30, 12:55 am, Daniel Lyons fus...@storytotell.org wrote: I don't see why that wouldn't be the case, if you were using Java's   native multidimensional arrays. I don't think it would be as much fun,   That's my point. It's often argued that you can just optimize the teeny bottleneck by

Re: Clojure for Scientific and other CPU-intensive Computing

2009-06-30 Thread Daniel Lyons
On Jun 30, 2009, at 3:53 AM, fft1976 wrote: On Jun 30, 12:55 am, Daniel Lyons fus...@storytotell.org wrote: I don't see why that wouldn't be the case, if you were using Java's native multidimensional arrays. I don't think it would be as much fun, That's my point. It's often argued

Clojure for Scientific and other CPU-intensive Computing

2009-06-29 Thread fft1976
Based on the recent survey What are people using Clojure for?, people are mostly using it for non-CPU-intensive work, like parsing, report generation, GUIs, glue code. It's been argued by some that Clojure is as fast as Java, because at worst, you can implement your bottlenecks in Java. I have a

Re: Clojure for Scientific and other CPU-intensive Computing

2009-06-29 Thread Richard Newman
I would be curious to know if anyone is using Clojure for CPU- intensive work where performance really counts. Respectfully, I wouldn't class telephony as non-CPU-intensive. :) Speed directly translates to calls-per-second. I've been very happy with Clojure thus far.

Re: Clojure for Scientific and other CPU-intensive Computing

2009-06-29 Thread fft1976
On Jun 29, 1:39 pm, Richard Newman holyg...@gmail.com wrote: I would be curious to know if anyone is using Clojure for CPU- intensive work where performance really counts. Respectfully, I wouldn't class telephony as non-CPU-intensive. :) I would have thought those kinds of things are

Re: Clojure for Scientific and other CPU-intensive Computing

2009-06-29 Thread Richard Newman
Respectfully, I wouldn't class telephony as non-CPU-intensive. :) I would have thought those kinds of things are bandwidth-limited. Typically not. Some rough numbers: a complete call setup and teardown is usually no more than 5KB, spread over the course of the call -- the initial