CPU Usage goes high with NOW SMS | Search |
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through January 22, 2009 ⬆ |
◄ ► |
Author | Message | ||||
Simranjit Singh |
Hi ! I am facing one problem. while running Now Sms CPU USAGE goes very high near abt 60-70% which slows down the CPU and sometimes CPU HANGES . How to rectify this. regards Simranjeet Singh | ||||
Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 7692 Registered: 10-2002 |
Hi, I'm sorry, I don't have any information about your configuration. Can you confirm that it is the SMSGWS.EXE process that is using a lot of CPU? How many SMSC connections do you have defined? What routing definitions do you have in place? It sounds to me like there's probably some sort of circular routing taking place. We've had some people who download the trial version of NowSMS and then try to connect it via HTTP to itself. I wish I had a better answer for you ... but basically we need a lot more description of your configuration. In particular, the SMSGW.INI file would be very helpful (just "x" out any sensitive usernames or passwords). And if nothing is obvious, enable the SMSDEBUG.LOG on the "Serial #" page of the NowSMS configuration. And post the details from the SMSDEBUG.LOG, as that will give us a better idea of what is happening. -bn | ||||
Simranjit Singh New member Username: Manchanda_17 Post Number: 2 Registered: 06-2007 |
Hi ! Please find attached LOGS as per requirement!! Kindly help me by resolving this. Regards Simranjeet Singh
| ||||
Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 7700 Registered: 10-2002 |
Ok ... that is 19 seconds worth of log files. I have a little more idea of your configuration, but not much. I see 3 SMS messages being submitted by NowSMS to an HTTP SMSC connection. How many messages are currently in the NowSMS outbound queue? CPU utilisation could be high simply because it is busy submitting messages. I'd need to see a log file that contains a longer period of data to have a more full understanding of your system. -bn | ||||
Simranjit Singh New member Username: Manchanda_17 Post Number: 3 Registered: 06-2007 |
Hi! Please find attached again SMSDEBUG Log File
| ||||
Simranjit Singh New member Username: Manchanda_17 Post Number: 4 Registered: 06-2007 |
Hi! Please find attached again SMSDEBUG Log File | ||||
Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 7702 Registered: 10-2002 |
I can only repeat my earlier comments/questions... How many messages are currently in the NowSMS outbound queue? CPU utilisation could be high simply because it is busy submitting messages. | ||||
Simranjit Singh New member Username: Manchanda_17 Post Number: 5 Registered: 06-2007 |
Approximatly 400-500msgs | ||||
Des - NowSMS Support Board Administrator Username: Desosms Post Number: 270 Registered: 08-2008 |
Assuming that you don't submit any more messages, and NowSMS is allowed to clear those 400 to 500 messages, does CPU utilisation then return to normal? -- Des NowSMS Support | ||||
Simranjit Singh New member Username: Manchanda_17 Post Number: 6 Registered: 06-2007 |
Hi Des! Thanks for replying. Yes CPU Usage comes to normal after Que Gets Cleared or If we stop the Service at that time too CPU Usage comes to normal. I have checked through Task Manager SMSGW.Exe is using CPU Memory upto 85-90% at the time of submitting Messages. My system configuration is Quite Good, Running Windows Server 2003 (SP2). Rgds Simranjeet Singh | ||||
Des - NowSMS Support Board Administrator Username: Desosms Post Number: 274 Registered: 08-2008 |
Hi, I assume that you mean that SMSGWS.EXE is the task that is consuming a lot of CPU time. The only unusual thing that I see in your brief debug logs above, is that there are multiple HTTP SMSC connections defined. However, there are connect errors being reported on all but the first HTTP SMSC connection (it looks like the server might only one HTTP connection). So perhaps there removing the other HTTP connections, and leaving only one will make a difference. Perhaps there is a virus scanner running which is monitoring all of the file activity. Some virus scanners can go crazy with all of the Q files that NowSMS creates. (Try temporarily turning off your virus scanner during a test to see if that is a factor.) Is this a trial version? If so, I'd recommend trying the latest version as well, as it is more efficient dealing with large message queues. However, that said, 400 to 500 messages in the queue is not a lot. -- Des NowSMS Support |