Pitiful benchmark performance

[Ulf Wiger]

On 9 Jun 2001, Sebastian Strollo wrote:


>*But* I ran the C, perl and the Erlang version of the test on
>the same machine and just the difference in wall clock is really
>big. I don't know what is going on? Any takers?

I don't know, but I've never had the impression that Erlang was
very quick to initialize. What happens if the clock is started
by triggering it inside an already running VM?

Also, I don't know how much it affects the benchmark, but sockets
basically behave like low-priority processes. This seems to work
OK in a system that handles large volumes of I/O and doing some-
thing significant with most of it (e.g. connection handling.)

/Uffe
-- 
Ulf Wiger                                    tfn: +46  8 719 81 95
Senior System Architect                      mob: +46 70 519 81 95
Strategic Product & System Management    ATM Multiservice Networks
Data Backbone & Optical Services Division      Ericsson Telecom AB