Re: SMPP throttling

"Bruno David Rodrigues" <[email protected]>
Newsgroups gmane.comp.mobile.kannel.devel
Message-ID <02c201c1c0cb$f6696180$603b0a0a@davi>
A perl script that forks itself (fork or threads), open the socket and
writes the
'GET /send... &to='. $number. '... HTTP/1.0\r\n\r\n', close the socket (or
keep it open, I don't remember how's the keepalive feature of smsbox), and
repeat until the end of the list ?

I've once done a perl script that forks itself 64 childs to do snmpget's at
every 5 minutes
The machine has a continuous load of 5 for more than one year. Then "they"
disconnected it :(


----- Original Message -----
From: "Stipe Tolj" <[email protected]>
To: "Bruno David Rodrigues" <[email protected]>
Cc: "Matthew Flax" <[email protected]>; <[email protected]>
Sent: Tuesday, February 26, 2002 10:20 AM
Subject: Re: SMPP throttling


> Bruno David Rodrigues wrote:
> >
> > I've done spam^H^H^H^Hmarketing with something like this:
> >
> > a text file with one msisdn per line
>
> the main issue was how to create an input stream to Kannel's HTTP
> sendsms interface with 300-400 concurrent messages.
>
> When we consider concurrent = "within the same second", then I think
> initiating 300-400 processes of lynx in *one* second is almost
> impossible for "normal" boxes.
>
> Basicly the concepts of load-testing and benchmarking apply in the
> same way as for traditional HTTP servers. I recommend some readings at
> http://researchindex.org/ for this, they have high-quality papers
> about that. But keep in mind, it's a very theoretical background.
>
> Stipe
>
> [email protected]
> -------------------------------------------------------------------
> Wapme Systems AG
>
> Münsterstr. 248
> 40470 Düsseldorf
>
> Tel: +49-211-74845-0
> Fax: +49-211-74845-299
>
> E-Mail: [email protected]
> Internet: http://www.wapme-systems.de
> -------------------------------------------------------------------
> wapme.net - wherever you are
>
>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.