How big is the store? Are you using spool with ext3? If the store spool builds up, ext3 could become a serious performance hog. I'd recommend you to use a separate ext2 partition for the spool dir, your performance will improve a lot (specially if you have to restart kannel with tens/hundreds of thousands messages on the spool).
Regards, Alex 2010/1/5 Rolandow <[email protected]> > Hi Nikos, > > I'd like to do a little follow up on this one .. I was wondering .. For a > project we are currently processing about 85 sms/sec, and we are pushing > them by calling the sendsms by HTTP get. > > The SMSc sais they limited their connection to 100 sms/sec. When I check > the load, cpu usage and memory usage, I see that most of it is being used by > kannel. > > Is it possible that this is caused by a queue that's building up? > > > Nikos Balkanas wrote: > >> Hi, >> On a mediocre system, if you bench it with fakesmsc you can reach 2000 >> MT/s (half as much for MO). In real life the bottleneck is the SMSc >> connection which accept only ~20 SMS/s (depending on contract) >> BR, >> Nikos >> >> ----- Original Message ----- >> *From:* Eric Michiels <mailto:[email protected]> >> *To:* [email protected] <mailto:[email protected]> >> *Sent:* Monday, January 04, 2010 7:23 PM >> *Subject:* SMS per second >> >> Hi, can anyone tell me up to how many sms per second can Kannel handle? >> >> thank you, >> >> Eric >> > > >
