NowSMS performance issue

NowSMS performance issue SearchSearch

SMS & MMS Technical Forum » NowSMS Support - SMS Issues (Product Support Only) » Archive through May 20, 2013 » NowSMS performance issue « Previous || Next »
Author Message
Chris
Frequent Contributor
Username: Chrisc

Post Number: 66
Registered: 12-2008
Posted on Monday, April 29, 2013 - 03:36 pm:   

Hi guys

We're currently testing the latest version of NowSMS (v2013.04.01) and we have noticed that the messaging throughput rate has slightly diminished when comparing it to the previous version (v2012.06.28) with it's accompanying character set dll patches.

In our testing environment, we have two SMS servers, both with NowSMS installed, both configured to 50 messages/second.

When batch testing 10,000 messages we can see the one server with the latest version is averaging approximately 38 messages /second, where the other server is averaging around 96 messages /second (taking burst rates into account).

In terms of hardware performance, it appears the first server displayed behaviour where it was hardly doing anything, which made us believe that the NowSMS software was deliberately holding messages back. The second server though, was actively using hardware to get the messages out as fast as possible during the time the batch was sent.

Would you be able to look into the current version to see if there aren't any performance limitations that may have been imposed?

Thank you

Regards
Chris
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 8064
Registered: 10-2002
Posted on Monday, April 29, 2013 - 08:32 pm:   

Hi Chris,

We're not seeing any issues where 50 messages per second is throttled down to less than 50 messages per second. However, this version spreads the messages more evenly over a minute as opposed to bursting a full minute's worth as quickly as possible.

That said, there may be a scenario that we have not fully considered where this could impact performance.

We will set the default back to bursty performance for the larger licenses. I expect we will be able to post an interim update tomorrow that reflects this change.


-bn

Bryce Norwood
Now SMS/MMS Support
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 4455
Registered: 08-2008
Posted on Tuesday, April 30, 2013 - 09:46 am:   

Follow-up.

An update has been posted at http://www.nowsms.com/download/nowsms20130430.zip to address this issue.

Larger licenses will return to a more burst driven type of performance, throttling per minute instead of per second.

--
Des
NowSMS Support
sam
Frequent Contributor
Username: Samdsouza

Post Number: 137
Registered: 08-2006
Posted on Saturday, May 04, 2013 - 08:27 am:   

Thanks for this Des:

* MMSC: Fix "Convert to Web Link" displaying the text @@CONTENTURLTYPE@@ if the processed content is forward locked.

"However, this version spreads the messages more evenly over a minute as opposed to bursting a full minute's worth as quickly as possible"

Above is the ideal way NowSMS should behave if you ask me..makes the server more stable...I mean the server hardware about be able to handle this even spreading more better...

Thanks once again.
Sam
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 4466
Registered: 08-2008
Posted on Saturday, May 04, 2013 - 01:21 pm:   

Hi Sam,

Yes, the more even spread of messages should make the server more stable ... especially for virtual machine environments which can be more sensitive to CPU spikes.

However, at higher speeds timing becomes more sensitive.

We have done more investigation of the issue described by Chris, as the fix here was to revert to earlier logic. We eventually hope to reintroduce the more even logic in the future (currently it is used only at speeds of 10 messages per second or lower), and plan to implement a setting for the more even spreading logic in case it is helpful in some environments for avoiding CPU spikes.

--
Des
NowSMS Support
sam
Frequent Contributor
Username: Samdsouza

Post Number: 139
Registered: 08-2006
Posted on Monday, May 06, 2013 - 04:22 am:   

Hi Des

Thanks for your reply. Highly appreciated. The even spreading logic is just brilliant. I have seen 8 core LAMP servers with 16gb RAM running at more then 90% with kannel. In short simply not able to handle the loads with messages getting queued up at the server.

I have still not got a chance to test/see the real world throughput's offered by NowSMS but the way you guys have designed it to work even on Windows is simply great.

In my opinion the default mode should be even mode and not the burst mode. Maybe you can provide a SMSGW.ini setting which would enable the burst mode if required. Having the default mode as burst mode would jam the server.

Regards
Sam
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 4484
Registered: 08-2008
Posted on Friday, May 17, 2013 - 07:45 pm:   

Hi Chris & Sam,

More follow-up on this issue.

We have posted another update at http://www.nowsms.com/download/nowsms20130515.zip.

By default it re-enables the new "evenflow" logic. We believe we have identified and fixed the issue that was causing this logic to over-throttle in some environments. If it is still limiting performance or is undesirable for unexpected reasons, this logic can be disabled by adding LicenseEvenFlow=No under the [SMSGW] header of SMSGW.INI. (For practical purposes, this setting has no effect unless license speeds are 10mps or higher.)

Related to this change, we are introducing an enhancement to our licensing, which we are referring to as "burst mode".

Burst mode is a licensing enhancement to help customers better handle bursts of activity. Instead of just tracking at message throughput per minute or second, NowSMS also keeps track of activity over the past hour, and allows unused throughput capacity during the previous hour to be applied as a performance burst. Performance burst activity will provide up to double the license throughput for up to 30 minutes.

For example, consider a 10 message per second license which has been completely idle with no messaging traffic for at least 30 minutes. A large bulk submission occurs and burst mode will be automatically activated to operate at 20 messages per second for 30 minutes. After 30 minutes, burst mode deactivates and the speed reverts to 10 messages per second.

That is an extreme example. In more typical usage scenarios, burst mode helps better manage the peaks and valleys of message traffic by applying the license speed cap on a rolling hour period, allowing unused capacity from the previous 60 minutes to be reclaimed with burst mode.

--
Des
NowSMS Support
sam
Frequent Contributor
Username: Samdsouza

Post Number: 143
Registered: 08-2006
Posted on Saturday, May 18, 2013 - 09:07 am:   

This is brilliant!!!! Absolutely brilliant...."evenflow" is a new benchmark on throughput's...would require Chris's inputs in real time testing...
Chris
Frequent Contributor
Username: Chrisc

Post Number: 67
Registered: 12-2008
Posted on Monday, May 20, 2013 - 02:53 pm:   

Hi Des - and Sam,

We'll be looking at testing the new version you released sometime soon I expect. We've got quite a few dealings going at the moment so I can't give an exact date on when we'll be testing.

Still, once I'm able to dig into the new version I'll test the different configuration scenarios you described and also relate my findings here.

Regards
Chris

Login Login / Register Logout Logout Search Last 30 Days Topics Topics