Budget Erlnag/OTP hardware

Ulf Wiger ulf@REDACTED
Tue Jan 18 07:26:22 CET 2005


The 3 msgs/sec indicates that just about any PC available
on the market would suffice, but that of course depends
on just how heavy the processing load per message is.
Also, if you're storing in Mnesia - do you store to disk?
If not, storing in Mnesia is very cheap; otherwise, the
load goes up.

As one performance reference, look at
which is one application using HTTP and SS7, and running
100 requests/sec on a Sun Netra T1.

But you should build a prototype and measure its
performance before you go out shopping for hardware.
Memory consumption is another issue you need to look
at. This is largely a factor of how much data you need
to hold in memory, but also keep in mind that Erlang
tends to allocate some memory dynamically (not quite
as heavily as Java, though.)

Regarding OS, assuming I'm correct in guessing that
performance will not be your biggest problem, you should
go with the OS that you're most comfortable with, and
which seems functionally suitable for the task.


Den 2005-01-18 00:07:22 skrev Stephen Han <kruegger@REDACTED>:

> Hi.
> If I have an Erlang application that,
> - uses MNESIA to store and delete incoming messages.
> - converts incoming messge to HTTP and forward it to Yaws running in
> same platform.
> - receives about 3 msgs/sec through TCP/IP.
> - heavily contructs and matches binary messages.
> - creates process per message.
> 1. What will be the value CPU for this kind of Erlang application? I
> saw some people using Celoron, P4 - hyperthreading, Sempron, Athlon 64
> or even VIA EPIA, too. I guess the more expensive, the better but
> there must be just enough CPU for those kind of tasks. Also could you
> tell me why?
> 2. If the Erlang/OTP is running x86 CPUs, what OS is a better choice
> in performance wise? Windows/Linux/FreeBSD?
> regards,

Använder Operas banbrytande e-postklient: http://www.opera.com/m2/

More information about the erlang-questions mailing list