[Asterisk-Dev] Benchmark numbers....

[niels at wxn.nl]

> But the real scalability wall I've seen is number of registered
peers...
> That's what takes down a box (at least with IAX). I've heard reports
of a
> Dual Xeon 3.2GHz not being able to handle even 1000 IAX peers. 
> -Michael

Michael is right... 

My dual 3.0 ghz xeon has problems when it hit's about 1000 users
registering every 60 seconds.. a dual processor doesn't help much by the
way.. asterisk mostly uses only one of using 99.9% cpu power and still
one processor doing nothing

I managed to get about 2500 users online on one box by modifying iax2.h
(reg expire changed from from 60 to 240 seconds) decent IAX clients will
comply with that setting .. b.t.w. don't go higher, because many NAT
gateways will close their dynamic NAT mappings after 300 secs, a few
some even after 30 secs!! 

#define IAX_DEFAULT_REG_EXPIRE  60 /* re-registration once per minute */

1000 users online (re-registering every 60 seconds) means 16
registrations per second... that's almost nothing!! good optimized code
should minimal be able to handle a thousand times as much regs per
second.. (take a look at SER for example)

The performance of asterisk's simultaneous calls is very good.. we know
that.. But the registration performance is really (let me call it)
pathetic... 

This just makes it impossible to handle a decent amount of users with
IAX, really too bad, This way IAX will never be able to meet with the
big standards, because the bigger guys just can't use it this way.