Re: Shared Memory, semaphores and a new "box"

On Tue, Mar 4, 2008 at 10:33 AM, Andreas Fink <[email protected]> wrote:
> I think the problem is not Kannel or HTTP, the problem is your way of using
> it in PHP.
>
> If you for example use something like file("http://localhost/sendsms=...")
> in php to send an SMS, PHP will stop and wait until Kannel has respondet to
> it. After that you can continue. This wont get you over something like 10
> sms/sec. However if you run 10 such PHP scripts in parallel, you will get
> 100 sms/sec without any problems. So the latency is caused by PHP waiting
> for the reply instead of continuing and preparing to requeue the next
> message. Parallelizing is the margic word here.
>
> So instead of full throttle, you will get stop & go.

don't think he's problem arrises there, I use PHP too, and I'm using
PHP's CURL functions for posting to Kannel's HTTP interface and it
goes really fast, you con post thousands of messages very quickly

But I agree that sqlbox handles it better, and much faster, you can
get many records by making a multiple values insert and will get much
faster than the HTTP interface.

Not sure why he would need MORE performance than that, but I agree
that generates you a dependancy on a DB
So he obviously wants to have a performance similar to the sqlbox one,
without the need of a DB

The thing is why he wants that, just for having scripts that send tons
and tons of messages finish faster (I like that) or what