Re: WebCatalog Eating 200% of the CPU
This WebDNA talk-list message is from 2002
It keeps the original formatting.
numero = 44828
interpreted = N
texte = This is not necessarily a bug with the engine. If you intentionally (or accidentally) create a template that performs 10s of thousands of searches, or that contains a huge number of iterations on a block of WebDNA code, to the point where it takes several minutes for the template to complete; then if that template is requested dozens of times within a few seconds, it would be easy to bring the engine to a crawl. This is why it is important for the WebDNA programmer (or any programmer) to exercise some caution with their code. It is always a good idea lookout for possible infinite or very large loops, redundant code, assumptions in form data, etc...It would be easy to write a C++ application that intentionally brings an OS to its knees, so would that be the fault of the OS?However, there are a couple of preferences that may help to prevent a WebDNA overload. The 'Max Search Results' was intended to prevent an accidental iteration of a large number of search results in the [founditems] loop. We have also added a new pref that allows you to control the maximum number of concurrent threads the WebDNA engine can spawn. Both of those may help. But again, there is no substitute for thorough testing of WebDNA template code before going to production.> -----Original Message----- > From: WebCatalog Talk > [mailto:WebDNA-Talk@talk.smithmicro.com]On Behalf > Of Alain Russell > Sent: Monday, November 04, 2002 6:00 PM > To: WebCatalog Talk > Subject: Re: WebCatalog Eating 200% of the CPU > > > No I think it is supposed to catch the 'Zombie' state - > perhaps a little > more work is needed ?? Perhaps this is why the 4.5 patch > seems to have been > delayed ;) > > > On 11/4/02 4:37 PM, Alain Russell >
wrote: > > > >> Aaron & I had a discussion about this the other day. > >> I've reported to SMSI a while ago about WebDNA doing this > with 'good' > >> searches when the pages are loaded .. > >> > >> Say you have a slow/big search that is coded right - hit > is a few times > >> quickly and this condition can happen. > >> > >> Check the archives for the discussion. > > > > Any response from Smith Micro? I thought WebCatalog > Monitor was supposed to > > catch these situations, or is that only when WebCatalog quits? > > > > Thanks > > > ------------------------------------------------------------- > 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/------------------------------------------------------------- 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:
This is not necessarily a bug with the engine. If you intentionally (or accidentally) create a template that performs 10s of thousands of searches, or that contains a huge number of iterations on a block of WebDNA code, to the point where it takes several minutes for the template to complete; then if that template is requested dozens of times within a few seconds, it would be easy to bring the engine to a crawl. This is why it is important for the WebDNA programmer (or any programmer) to exercise some caution with their code. It is always a good idea lookout for possible infinite or very large loops, redundant code, assumptions in form data, etc...It would be easy to write a C++ application that intentionally brings an OS to its knees, so would that be the fault of the OS?However, there are a couple of preferences that may help to prevent a WebDNA overload. The 'Max Search Results' was intended to prevent an accidental iteration of a large number of search results in the [founditems] loop. We have also added a new pref that allows you to control the maximum number of concurrent threads the WebDNA engine can spawn. Both of those may help. But again, there is no substitute for thorough testing of WebDNA template code before going to production.> -----Original Message----- > From: WebCatalog Talk > [mailto:WebDNA-Talk@talk.smithmicro.com]On Behalf > Of Alain Russell > Sent: Monday, November 04, 2002 6:00 PM > To: WebCatalog Talk > Subject: Re: WebCatalog Eating 200% of the CPU > > > No I think it is supposed to catch the 'Zombie' state - > perhaps a little > more work is needed ?? Perhaps this is why the 4.5 patch > seems to have been > delayed ;) > > > On 11/4/02 4:37 PM, Alain Russell > wrote: > > > >> Aaron & I had a discussion about this the other day. > >> I've reported to SMSI a while ago about WebDNA doing this > with 'good' > >> searches when the pages are loaded .. > >> > >> Say you have a slow/big search that is coded right - hit > is a few times > >> quickly and this condition can happen. > >> > >> Check the archives for the discussion. > > > > Any response from Smith Micro? I thought WebCatalog > Monitor was supposed to > > catch these situations, or is that only when WebCatalog quits? > > > > Thanks > > > ------------------------------------------------------------- > 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/------------------------------------------------------------- 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/
Scott Anderson
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:
Running 2 two WebCatalog.acgi's (1996)
Showif, Hideif reverse logic ? (1997)
object tag examples (2004)
WebCatalog f2 Installation (1997)
OT: Apache ServerAlias (2003)
Mixing and/or in searches (1998)
Carrying Forward (1998)
catagories (1997)
What am I missing (1997)
Mapping .tmpl extension on NT (1998)
[SearchString] usage (1997)
[WebDNA] How to valuate a domain name? (2010)
RE: [WebDNA] JSONStore Levels (2020)
WebCatalog 2.0 & WebDNA docs in HTML ... (1997)
Emailer (WebCat2) (1997)
Changing the value assigned to a formvariable (2000)
help with duplicate records posted (1998)
Using Plug-In while running 1.6.1 (1997)
limitation found on group searching (1997)
Multiple download orders of the same product? (1997)