Re: Freeze
This WebDNA talk-list message is from 2003
It keeps the original formatting.
numero = 47640
interpreted = N
texte = I do not think that would be the problem.The engine creates a temporary file when outputting the database from RAM to disk (instead of overwriting the original db file contents). The original database file is then deleted, and the temp file is renamed to the original db name. So the only extra 'cost' when using this 'Safe DB Write' feature is the amount of time it takes the OS to delete the original db file, and rename the temp file.This feature can be disabled via the WebDNA admin preferences page. > -----Original Message----- > From: WebDNA Talk [mailto:WebDNA-Talk@talk.smithmicro.com]On Behalf Of > Kenneth Grome > Sent: Monday, February 10, 2003 5:50 PM > To: WebDNA Talk > Subject: Re: Freeze > > > >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/------------------------------------------------------------- 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:
I do not think that would be the problem.The engine creates a temporary file when outputting the database from RAM to disk (instead of overwriting the original db file contents). The original database file is then deleted, and the temp file is renamed to the original db name. So the only extra 'cost' when using this 'Safe DB Write' feature is the amount of time it takes the OS to delete the original db file, and rename the temp file.This feature can be disabled via the WebDNA admin preferences page. > -----Original Message----- > From: WebDNA Talk [mailto:WebDNA-Talk@talk.smithmicro.com]On Behalf Of > Kenneth Grome > Sent: Monday, February 10, 2003 5:50 PM > To: WebDNA Talk > Subject: Re: Freeze > > > >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/------------------------------------------------------------- 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/
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:
The USArea® Network web site ... (1997)
IE drops support (2004)
F3 crashing server (1997)
Beta (?) version of WebCatalog 2.1 (1998)
problems with 2 tags (1997)
[FileInfo] (1998)
[WebDNA] WebDNA code displaying on page (2012)
WebCat2b14MacPlugIn - [include] doesn't hide the search string (1997)
[AppendFile] problem (WebCat2b13 Mac .acgi) (1997)
Javascript/WebCatalog form population (2001)
cart file creation (2003)
Tab Charactor (1997)
Database flushing does not work any more... (2000)
More questions about serial number dishing (1997)
WebCat b13 CGI -shownext- (1997)
[WebDNA] High-profile WebDNA sites? (2008)
Hideif not working? (2001)
[isfile] ? (1997)
Can you do this??? and other stuff (1997)
Emailer choke (1997)