Re: Server Freeze
This WebDNA talk-list message is from 1998
It keeps the original formatting.
numero = 17854
interpreted = N
texte = >> >>Also, when sending mass quantities of email, the server locks up while >> >>WebCatalog writes out 5500 files to the outgoing email directory this >> takes >> >>3 to 5 minutes while the server can't be used. >> > >> >It takes a while to write 5500 new text files to disk. The MacOS has to >> >catalogue them as they are created, so the delay is most likely not a >> >WebCatalog issue, it's probably an issue related to the speed of the >> MacOS itself. >> >> I don't have a problem with the speed, I'd be happy if it took 15 >> minutes, >> I'm not expecting a miracle here, I realize Hard drive access is required >> for this. I'm annoyed that the webserver can't be used as a web server >> while >> this is happening. It is an insult that ANY program running on ANY server >> should monopolize 100% of the CPU time. >> >I am sure glad I read this thread. I was just about to plunk down the cash >on web cat but there is NO WAY if it essentially shuts down the server to >process. Threading is needed.Before you all go off the deep end and start believing that WebCat tends to have any problems with multi-threading in its everyday processing, let me tell you right now that it does NOT. In fact, I'm not all that sure that it really has any multi-threading problems at all!Just because I was trying to use WebCatalog in a particular manner does not mean that I *should be*. And another poster was correct when he said that Brian would be far better off if he were using WebCatalog to create *ONE* email message and send that message to a list server -- instead of trying to turn WebCatalog into a listserver.And there's other ways of dealing with this if you simply *must* make WebCat create all thuse messagee -- such as splitting the process into smaller chunks then processing one chunk at a time.WebCat's a really cool tool because it's flexible, powerful and it does so many different tasks so quickly and so well. But just because it can do one task very effectively does not mean you should assume that it can repeat that same task 5000 or 10,000 times in a row without *some* kind of negative effect on performance.All that's really necessary here is to be aware of the *potential* for slowdowns to occur based on your knowledge of the task you're asking WebCat to perform. Then if you're creating the environment for a potential slowdown situation, you can usually deal with it -- without giving up on WebCat entirely.Sincerely, Ken Grome 808-737-6499 WebDNA Solutions mailto:ken@webdna.net http://www.webdna.net
Associated Messages, from the most recent to the oldest:
>> >>Also, when sending mass quantities of email, the server locks up while >> >>WebCatalog writes out 5500 files to the outgoing email directory this >> takes >> >>3 to 5 minutes while the server can't be used. >> > >> >It takes a while to write 5500 new text files to disk. The MacOS has to >> >catalogue them as they are created, so the delay is most likely not a >> >WebCatalog issue, it's probably an issue related to the speed of the >> MacOS itself. >> >> I don't have a problem with the speed, I'd be happy if it took 15 >> minutes, >> I'm not expecting a miracle here, I realize Hard drive access is required >> for this. I'm annoyed that the webserver can't be used as a web server >> while >> this is happening. It is an insult that ANY program running on ANY server >> should monopolize 100% of the CPU time. >> >I am sure glad I read this thread. I was just about to plunk down the cash >on web cat but there is NO WAY if it essentially shuts down the server to >process. Threading is needed.Before you all go off the deep end and start believing that WebCat tends to have any problems with multi-threading in its everyday processing, let me tell you right now that it does NOT. In fact, I'm not all that sure that it really has any multi-threading problems at all!Just because I was trying to use WebCatalog in a particular manner does not mean that I *should be*. And another poster was correct when he said that Brian would be far better off if he were using WebCatalog to create *ONE* email message and send that message to a list server -- instead of trying to turn WebCatalog into a listserver.And there's other ways of dealing with this if you simply *must* make WebCat create all thuse messagee -- such as splitting the process into smaller chunks then processing one chunk at a time.WebCat's a really cool tool because it's flexible, powerful and it does so many different tasks so quickly and so well. But just because it can do one task very effectively does not mean you should assume that it can repeat that same task 5000 or 10,000 times in a row without *some* kind of negative effect on performance.All that's really necessary here is to be aware of the *potential* for slowdowns to occur based on your knowledge of the task you're asking WebCat to perform. Then if you're creating the environment for a potential slowdown situation, you can usually deal with it -- without giving up on WebCat entirely.Sincerely, Ken Grome 808-737-6499 WebDNA Solutions mailto:ken@webdna.net http://www.webdna.net
Kenneth Grome
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:
NT 4.0/IIS WebCat Installation (1998)
Nested vs conditional (1997)
WebCommerce: Folder organization ? (1997)
AppleScript: Tell application:app location? (1998)
[WebDNA] mac osx permissions problem (2010)
Problems with [Search] param - Mac Plugin b15 (1997)
WebCat2b15MacPlugIn - [authenticate] not [protect] (1997)
Users.db [encrypt seed=????] (1998)
Nested Loops and SHOWIFs (1997)
FREE Stuff .. (2003)
WebCat2b12--[searchstring] bug (1997)
Cant open pages generated by Webcat (2004)
Emailer Problem (1999)
[ListFiles] & [loop] (1998)
Single Link browsing (1997)
WebCat/Typhoon Status under Windows (1998)
HTML Editors (1997)
Max Record length restated as maybe bug (1997)
Next (1997)
OT- OSX / OSX Server... (2004)