Re: WebCatalog Eating 200% of the CPU
This WebDNA talk-list message is from 2002
It keeps the original formatting.
numero = 44857
interpreted = N
texte = Someone discounted this earlier but I thought I'dpost a tid-bit. (since the maker of our softwarenow works for blueworld).There has been a long and on-going thread aboutCPU cycling (CPU hog) on the webStar list. Lassohas come up in the thread quite often. Here is whatCJ (lead programmer) last said about it.______________________________________________________________On Monday, November 4, 2002, at 04:10 PM, Stephen Lewis wrote:> When WSWebServer process was hogging (by looking at TOP), lsof> revealed a> few oddities, perhaps they mean something, perhaps not:>> COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME>> There were a couple of these:> WSWebServ 9788 webstar 51u inet 0t0 TCP no> PCB,> CANTSENDMORE, CANTRCVMORE>> But more interestingly there were SEVERAL of these:> WSWebServ 9788 webstar 43u inet 0x060c3a4c 0t0 TCP> localhost:51297->localhost:14550 (CLOSE_WAIT)> WSWebServ 9788 webstar 54u inet 0x062114cc 0t0 TCP> localhost:51059->localhost:14550 (CLOSE_WAIT)Our current theory, which seems to be confirmed by the folks atBlueWorld, is that there's a problem with the loop that Lasso uses toread data from HTTP client connection. (The usual didn't break fromloop when 0 bytes are received issue.) This is causing some infiniteloops in multiple threads. Meanwhile, connections to the Lasso serverare still outstanding. I'm guessing that either the server is timingout these connections, or the communication with Lasso server isalready finished and the plug-in is just reading extra data off ofthe connection (which is the proper thing to do). Either way, you getthese cpu hogging threads on the one hand, and half-closed connectionson the other.We have a new build for our beta testers, and we'll let people know asthis progresses. We changed our API to let Lasso know explicitly whenthe HTTP client connection closes, and BlueWorld says they'll changethe loop on their end, too.cjh______________________________________________________________Hope this helps,DonovanScott Anderson wrote:> TIME> ELAPSED-TIME> AVAILABLE MEMORY> CLIENT ADDRESS> PATH ARGUMENTS> PHYSICAL TEMPLATE PATH> CLIENT AGENT> USERNAME> PASSWORD> REFERRER> TEMPLATE NAME> DOC ROOT PREFIX> FORM DATA> COOKIE DATA> MIME HEADERS>> There is a bug with the ELAPSED-TIME data, it is tracked globally and is> therefore not accurate when running in multithreaded mode.>> You should also enable the 'Error Logging' pref. This will log any WebDNA> errors that occur during template processing.-- Donovan D. BrookeAdministrator of IT/Assc. Art DirectorEpsen Hillmer GraphicsHG Professional Forms-------------------------------------------------------------This message is sent to you because you are subscribed to the mailing list
.To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://search.smithmicro.com/
Associated Messages, from the most recent to the oldest:
Someone discounted this earlier but I thought I'dpost a tid-bit. (since the maker of our softwarenow works for blueworld).There has been a long and on-going thread aboutCPU cycling (CPU hog) on the webStar list. Lassohas come up in the thread quite often. Here is whatCJ (lead programmer) last said about it.______________________________________________________________On Monday, November 4, 2002, at 04:10 PM, Stephen Lewis wrote:> When WSWebServer process was hogging (by looking at TOP), lsof> revealed a> few oddities, perhaps they mean something, perhaps not:>> COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME>> There were a couple of these:> WSWebServ 9788 webstar 51u inet 0t0 TCP no> PCB,> CANTSENDMORE, CANTRCVMORE>> But more interestingly there were SEVERAL of these:> WSWebServ 9788 webstar 43u inet 0x060c3a4c 0t0 TCP> localhost:51297->localhost:14550 (CLOSE_WAIT)> WSWebServ 9788 webstar 54u inet 0x062114cc 0t0 TCP> localhost:51059->localhost:14550 (CLOSE_WAIT)Our current theory, which seems to be confirmed by the folks atBlueWorld, is that there's a problem with the loop that Lasso uses toread data from HTTP client connection. (The usual didn't break fromloop when 0 bytes are received issue.) This is causing some infiniteloops in multiple threads. Meanwhile, connections to the Lasso serverare still outstanding. I'm guessing that either the server is timingout these connections, or the communication with Lasso server isalready finished and the plug-in is just reading extra data off ofthe connection (which is the proper thing to do). Either way, you getthese cpu hogging threads on the one hand, and half-closed connectionson the other.We have a new build for our beta testers, and we'll let people know asthis progresses. We changed our API to let Lasso know explicitly whenthe HTTP client connection closes, and BlueWorld says they'll changethe loop on their end, too.cjh______________________________________________________________Hope this helps,DonovanScott Anderson wrote:> TIME> ELAPSED-TIME> AVAILABLE MEMORY> CLIENT ADDRESS> PATH ARGUMENTS> PHYSICAL TEMPLATE PATH> CLIENT AGENT> USERNAME> PASSWORD> REFERRER> TEMPLATE NAME> DOC ROOT PREFIX> FORM DATA> COOKIE DATA> MIME HEADERS>> There is a bug with the ELAPSED-TIME data, it is tracked globally and is> therefore not accurate when running in multithreaded mode.>> You should also enable the 'Error Logging' pref. This will log any WebDNA> errors that occur during template processing.-- Donovan D. BrookeAdministrator of IT/Assc. Art DirectorEpsen Hillmer GraphicsHG Professional Forms-------------------------------------------------------------This message is sent to you because you are subscribed to the mailing list .To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://search.smithmicro.com/
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:
Beta Documentation (1997)
(2002)
japanese characters (1997)
ASCII Code 127 (2004)
SQLResult chokes on null values? (2006)
wierd [cart] action! (1997)
[OT] Airport Problem (2003)
Forwarding Orders Via Email (1998)
Help (1999)
WebCat2final1 crashes (1997)
Fields/Forms Processing (1998)
Grep and Special Characters (2002)
shortening the cart (1998)
Showing specific [cart] contents (1998)
CMSBuilder (2004)
Subject: Authenticating users without dialog box (1997)
Preventing code execution (2003)
New Mac Emailer... (1997)
cart (1997)
[TaxableTotal] - not working with AOL and IE (1997)