Re: Freeze
This WebDNA talk-list message is from 2003
It keeps the original formatting.
numero = 47631
interpreted = N
texte = >On 2/10/03 4:35 PM, John Hill
wrote: > >> Could it be flushing large databases to disk after doing the requisit number >> of append/updates? That could tie up the machine. >Yep good thought.... The problem is the regularity.I think it's the way the new version of webdna is programmed to prevent db file corruption ... From my understanding (and please correct me if I'm wrong) webdna 4.5.1 is the first version to automatically write out a temporary copy of whatever db it's writing to -- every time it writes to a db. Then it deletes this temporary file after it has successfully written the appropriate changes to the 'real' db file.Didn't SMSI say they implemented this behavior in order to protect against data loss in the event of a crash?I think they made this the default behavior in 4.5.1 because some people had been complaining about losing data and/or getting corrupted db files when a crash occurred at the same time that webdna was writing to the file. Unfortunately what I do not know is if they gave us an option to turn off this new feature, or if we have no choice but to deal with the new problems it creates for us.My gut feeling is that the server may seem like it is taking a break (apparently refusing to respond for 5-15 seconds) every time a person accesses a page that writes something to a db file.Is this possibly what's going on?I have noticed a slow response from my remote server as well, but until now it never occurred to me that it was a problem with the webdna software. After all, I'm thousands of miles away from my server and not always on a consistent or reliable connection.But if this has nothing to do with my connection and everything to do with the way this version of webdna is coded, it would be very nice to learn that there's a preference that lets us shut off this unnecessary temporary file writing.Personally I've never had any problems with webdna destroying a db file upon a crash. And it would not create a problem for me anyways, because long ago I created a template-based system that automatically backs up all my db files every hour or every day.Personally I would prefer the server to be as fast as possible, and NEVER write or delete temporary db files upon every append or replace or delete -- as it may be doing now ... Sincerely, Kenneth Grome--------------------------------------------------- WebDNA Professional Training and Development Center 175 J. Llorente Street +63 (32) 255-6921 Cebu City, Cebu 6000 kengrome@webdna.net Philippines http://www.webdna.net ---------------------------------------------------------------------------------------------------------------- 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://webdna.smithmicro.com/
Associated Messages, from the most recent to the oldest:
>On 2/10/03 4:35 PM, John Hill wrote: > >> Could it be flushing large databases to disk after doing the requisit number >> of append/updates? That could tie up the machine. >Yep good thought.... The problem is the regularity.I think it's the way the new version of webdna is programmed to prevent db file corruption ... From my understanding (and please correct me if I'm wrong) webdna 4.5.1 is the first version to automatically write out a temporary copy of whatever db it's writing to -- every time it writes to a db. Then it deletes this temporary file after it has successfully written the appropriate changes to the 'real' db file.Didn't SMSI say they implemented this behavior in order to protect against data loss in the event of a crash?I think they made this the default behavior in 4.5.1 because some people had been complaining about losing data and/or getting corrupted db files when a crash occurred at the same time that webdna was writing to the file. Unfortunately what I do not know is if they gave us an option to turn off this new feature, or if we have no choice but to deal with the new problems it creates for us.My gut feeling is that the server may seem like it is taking a break (apparently refusing to respond for 5-15 seconds) every time a person accesses a page that writes something to a db file.Is this possibly what's going on?I have noticed a slow response from my remote server as well, but until now it never occurred to me that it was a problem with the webdna software. After all, I'm thousands of miles away from my server and not always on a consistent or reliable connection.But if this has nothing to do with my connection and everything to do with the way this version of webdna is coded, it would be very nice to learn that there's a preference that lets us shut off this unnecessary temporary file writing.Personally I've never had any problems with webdna destroying a db file upon a crash. And it would not create a problem for me anyways, because long ago I created a template-based system that automatically backs up all my db files every hour or every day.Personally I would prefer the server to be as fast as possible, and NEVER write or delete temporary db files upon every append or replace or delete -- as it may be doing now ... Sincerely, Kenneth Grome--------------------------------------------------- WebDNA Professional Training and Development Center 175 J. Llorente Street +63 (32) 255-6921 Cebu City, Cebu 6000 kengrome@webdna.net Philippines http://www.webdna.net ---------------------------------------------------------------------------------------------------------------- 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://webdna.smithmicro.com/
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:
"Advanced" Search Algorithm (2008)
WebCat2b13MacPlugin - [math][date][/math] problem (1997)
Initiating NewCart (1997)
Keep away (1997)
Eudora Plugin (1999)
Carriage Returns on mail receipt (2002)
Mozilla/4. and Browser Info.txt (1997)
[cart] tag (2000)
Live Webcasts (1999)
[WebDNA] [append] does not add the newline char at the end of the new record?! (which causes subsequent [search] to fail.) (2009)
WebCatalog NT beta 18 now available (1997)
Re:E-Mailer (WebCatb15acgiMac) (1997)
Replace context problem ... (1997)
cybercash on OSX - was Executing remote AppleScript (2000)
wierd [cart] action! (1997)
If Empty ? (1997)
What is WebDNA (1997)
WebCat2b13MacPlugIn - [include] doesn't allow creator (1997)
New public beta available (1997)
listfiles-looking for slick solution (1997)