Re: [WebDNA] Processor usage off the charts

This WebDNA talk-list message is from

2008


It keeps the original formatting.
numero = 101323
interpreted = N
texte = Tony Miller wrote: > Anyone know what would cause WebCatalog 6.0a to take 80-90% of the > processor and bog the whole machine down to almost stopped? > > Does it just take the remaining processor available or something? It is > constantly hogging the processor. > > Do I have a security breach or is this normal? > > Thanks > > Tony Miller > tmiller@thehawkeye.com Short bursts of high CPU usage may not be bad. However, if you have consistant issues with high CPU usage, there is probably something wrong. My experience shows that 98% of the time, the problem is in the code that is running, however, high CPU usage can be caused by many things. First, look in the admin pages.. is your: "Log error messages" and "Catching terminate signal", turned on? Sometimes, if these *trouble shooting* settings are *left on*, these files can grow to be huge and cause problems in themselves. If they are not on, turning them on temporarily can sometimes reveal where issues are. Another common issue may be heavy searches that are hit by SEO bots and other (DOS) type of calls. This can be corrected by dissallowing (perhaps in the robots.txt file) certain process heavy areas of the site. Looking at server managment from this perspective may help: When coding WebDNA, be sensitive to the question: What would this code do if it was hit hard? Other than these types of generalities, it is difficult to troubleshoot webserver problems without some clues... at the minimum, server specs and scope of code that is running on the server. Preferrably, you would have some isolated code.. perhaps using errors found in those two log files that I talked about, to go by. Lastly, the standard WebServer logs are good for checking for heightened traffic, and to what kind of calls, when you are having problems. Donovan -- Donovan D. Brooke PH/FAX: 1 (608) 291-2024 ---------------------------------------------- VP WebDNA Software Corporation 16192 Coastal Highway Lewes, DE 19958 Associated Messages, from the most recent to the oldest:

    
  1. Re: [WebDNA] Processor usage off the charts (Donovan Brooke 2008)
  2. Re: [WebDNA] Processor usage off the charts (Donovan Brooke 2008)
  3. Re: [WebDNA] Processor usage off the charts (Tony Miller 2008)
  4. Re: [WebDNA] Processor usage off the charts (rupert ravens 2008)
  5. Re: [WebDNA] Processor usage off the charts (Tony Miller 2008)
  6. Re: [WebDNA] Processor usage off the charts (Donovan Brooke 2008)
  7. [WebDNA] Processor usage off the charts (Tony Miller 2008)
Tony Miller wrote: > Anyone know what would cause WebCatalog 6.0a to take 80-90% of the > processor and bog the whole machine down to almost stopped? > > Does it just take the remaining processor available or something? It is > constantly hogging the processor. > > Do I have a security breach or is this normal? > > Thanks > > Tony Miller > tmiller@thehawkeye.com Short bursts of high CPU usage may not be bad. However, if you have consistant issues with high CPU usage, there is probably something wrong. My experience shows that 98% of the time, the problem is in the code that is running, however, high CPU usage can be caused by many things. First, look in the admin pages.. is your: "Log error messages" and "Catching terminate signal", turned on? Sometimes, if these *trouble shooting* settings are *left on*, these files can grow to be huge and cause problems in themselves. If they are not on, turning them on temporarily can sometimes reveal where issues are. Another common issue may be heavy searches that are hit by SEO bots and other (DOS) type of calls. This can be corrected by dissallowing (perhaps in the robots.txt file) certain process heavy areas of the site. Looking at server managment from this perspective may help: When coding WebDNA, be sensitive to the question: What would this code do if it was hit hard? Other than these types of generalities, it is difficult to troubleshoot webserver problems without some clues... at the minimum, server specs and scope of code that is running on the server. Preferrably, you would have some isolated code.. perhaps using errors found in those two log files that I talked about, to go by. Lastly, the standard WebServer logs are good for checking for heightened traffic, and to what kind of calls, when you are having problems. Donovan -- Donovan D. Brooke PH/FAX: 1 (608) 291-2024 ---------------------------------------------- VP WebDNA Software Corporation 16192 Coastal Highway Lewes, DE 19958 Donovan Brooke

DOWNLOAD WEBDNA NOW!

Top Articles:

Talk List

The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...

Related Readings:

[Summary] re: Emailer setup (1997) RE: Answer: WebDelivery downloads alias, not original ? (1997) RE: error count with $purchase (1997) Does anyone have any Whois lookup code in WebCat? (2007) mass mailing (1998) Practice runs ? (1997) Referrer problem - Truncation (1998) Emailer Problem (1998) emailer (1997) Tab Charactor (1997) Pop-up menu (1998) upgrading (1997) Here's how to kill a Butler Database. (1997) creating a ShipCosts database (1997) Allow/Deny with Webcat? (1998) Automatic POST arg sending? (1998) RE: type 2 errors with ssl server (1997) with Link i need to (1997) Search for dates greater than [date] (1997) redirect with frames (1997)