Parallelism (Re: Erlang rocks (Re: Eppur si sugat))

Eric Newhuis enewhuis@REDACTED
Thu May 29 16:47:59 CEST 2003

Megabyte arrays?  Need to analyze billions of records in seconds?

It might be a job for a vector-friendly language.  Try K?

I use K for our time-series database to store every trade there ever 
was.  1000s of records per second all day long five days per week 
forever.  (I've been working on a K-Erlang IPC bridge.  So far so 
good.)  But K and Erlang are oil and water.

Parallelism:  One thing that makes Erlang nice for parallelism is that 
it is easier to migrate processes among physical computing nodes.  I do 
a lot of parallel stuff with gobs of data stored in RAM for the fastest 
throughput and response-time possible.  And it is critical to be able to 
spread 1000s of processes among 100s of servers with little 
administrative overhead.

Erlang is perfect for this.

C++ is sub-optimnal for this, even when one uses specialized libraries.  
The memory bugs alone will kill you.

More information about the erlang-questions mailing list