Hammad,

The main bottleneck is usually the applications, not Kannel itself.

If your applications spent just a couple of seconds responding, at that rate
messages will start to pile up, deplete your available sockets and finally
sent your system(s) to a crawl.

So, first of all, applications and gateway should be on separate servers.

Depending on your application's design and load, you may consider a separate
db server or even clustering for apps.

Regarding Kannel, it's design is very efficient and nice on the CPU, so you
won't need that dual-xeon with gazillion gigs of ram, but you should anyway
put some decent hardware if you expect to manage hundreds of messages per
second.

I cannot give you specific specs, because there are too many variables that
can affect the overcome, but as a rule of thumb: many cores or HT are always
welcome, as well as memory. HD's not the main point of concern, since Kannel
does a lot of it's stuff on memory, but if you use MySQL storage for DLR's
or sqlbox, it may also play a role. You could use a separate DB here as
well.

As I've said before, your main point of concern is depletion of sockets
because application's delays, so plan that part well and you'll be well on
your path to succeed.

Regards,

Alejandro

On Dec 10, 2007 12:20 PM, Khan, Hammad Aslam <[EMAIL PROTECTED]> wrote:

> Thanks Juan.
>
> Anyone who can also share there experience about how much dedicated speed
> should be enough to run kannel supporting a max of 200sms/s?
> Regards,
> Hammad
>
> ---------- Forwarded message ----------
> From: "Juan Nin" <[EMAIL PROTECTED]>
> To: "Khan, Hammad Aslam" < [EMAIL PROTECTED]>
> Date: Sun, 9 Dec 2007 16:41:46 -0200
> Subject: Re: Kannel Deployment
> this question is not for the devel list, it's for the users one...
>
> anyway.. for SMPP traffic it's not the SMSC who has to connect to you
> Kannel box
> it's your kannel box which connects to the SMSC
>
> so u just NAT the traffic from you kannel box on your gateway and that's
> it
> (if it was the SMSC which connected to the kannel box, u could do a
> port forwarding)
>
> Regards,
>
> Juan
>
> On Dec 9, 2007 2:33 PM, Khan, Hammad Aslam <[EMAIL PROTECTED]> wrote:
> > Hi all,
> >
> > I know everyone who have used kannel in production here will have
> > deployments with more or less;
> > 1- Server running Kannel Gateway
> > 2- Server running HTTP Services
> >  3- A VPN Concentrator/Router/ADSL router with assigned static public IP
> to
> > interact with operator SMSCs
> >
> > I am currently setting up the above setup with ADSL Router at (3)
> >
> > I am stuck with misconception or what should I call it - My public IP is
> > assigned to router's external interface; and
> > Kannel machine is now in the private network (connected to the ADSL
> router's
> > through a switch to which Services comp is also connected).
> >
> > Now,
> > 1-how can kannel machine be visible to operator smsc? (through SMPP
> > connection) so that operator connect with kannel at port=13000
> -Suggested
> > network setup?
> > 2-How much dedicated speed is required if I connect to two operators'
> SMSC
> > where expected traffic is max 200sms/sec?
> >
> > Thanking in acticipation for resolution/suggestions.
> >
> > Regards,
> > Hammad
>
>
>
> _______________________________________________
> devel mailing list
> [EMAIL PROTECTED]
> http://www.kannel.org/mailman/listinfo/devel
>
>
>


-- 
Alejandro Guerrieri
Magicom
http://www.magicom-bcn.net/
LinkedIn: http://www.linkedin.com/in/aguerrieri

Reply via email to