OLOTU Olayinka wrote:
Hello All;
i have a running Kannel 1.4.0 WAP Gateway running with one wapbox on an HP
DL560 server
running Redhat AS 3.
I'd like to know how many concurrenct user connections that a wapbox can
handle, and
the effect [if any] of using more than a single wapbox, i.e what scale of
increase in
connection capacity would the addition of another wapbox bring?
Hello Bayo,
now, the load-capacity of Kannel acting as WAP GW can be as follows:
Linux 1x CPU Xeon 3.4G, 2GB RAM handles arround 200-250 req concurrent
Linux 8x CPU Xeon MP 2.7G, 4 GB RAM handles arround 750-800 req concurrent
now these are local benchmark testing.
When using in a real-work production environment you will have for the first
example arround 180-200 concurrent connections handling.
Kannel is designed to spread the load across wapboxes, so each wapbox handles a
queue of req. Using 2 wapbox means: un-blocking requests that fly throu the
system.... and so on
Now using more and more wapboxes has a draw-back. At bearerbox we need to route
the WDP datagrams to the corret wapbox.
Usually optimum is something between 2,3,4 wapboxes. Not more. I suggest trying
2.
If you need further support, please let me know.
Stipe
-------------------------------------------------------------------
Kölner Landstrasse 419
40589 Düsseldorf, NRW, Germany
tolj.org system architecture Kannel Software Foundation (KSF)
http://www.tolj.org/ http://www.kannel.org/
mailto:st_{at}_tolj.org mailto:stolj_{at}_kannel.org
-------------------------------------------------------------------
