Re: Freeze
This WebDNA talk-list message is from 2003
It keeps the original formatting.
numero = 47635
interpreted = N
texte = If the problem is as I described, more RAM will not help. Every time webdna writes to disk, it requires interaction with the OS. Slower OS's and larger db's obviously take more time to write to disk than smaller db's and faster OS's ...And if you have a lot of visitors appending, replacing or deleting records in your db's, that's going to increase the disk hits tremendously -- and slow everything down. >Hmmm... > >You may be on to something. I've been noticing my 4.5.1 server has >been unbelievably slow the last couple of weeks. Seems like that's >about when I upgraded to 4.5.1 > >I wonder if another half gig or so of ram would help...? > >> >-- > >Will Starck >NovaDerm Skincare Science >http://www.novaderm.com >wjs@novaderm.com > > >On Monday, February 10, 2003, at 07:50 PM, Kenneth Grome wrote: > >>> 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/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:
If the problem is as I described, more RAM will not help. Every time webdna writes to disk, it requires interaction with the OS. Slower OS's and larger db's obviously take more time to write to disk than smaller db's and faster OS's ...And if you have a lot of visitors appending, replacing or deleting records in your db's, that's going to increase the disk hits tremendously -- and slow everything down. >Hmmm... > >You may be on to something. I've been noticing my 4.5.1 server has >been unbelievably slow the last couple of weeks. Seems like that's >about when I upgraded to 4.5.1 > >I wonder if another half gig or so of ram would help...? > >> >-- > >Will Starck >NovaDerm Skincare Science >http://www.novaderm.com >wjs@novaderm.com > > >On Monday, February 10, 2003, at 07:50 PM, Kenneth Grome wrote: > >>> 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/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:
E-mail loop ! (1997)
Setting up WebCatalog with Retail Pro data (1996)
RE: EXTERNAL EMAIL: [WebDNA] IF statement evaluation bug report, (2019)
WebCat for Site Search? (1997)
Preventing code execution (2003)
Grant, please help me ... (1997)
I'm new be kind (1997)
Problems passing [SKU] with $Replace in 2.0 (1997)
Changes to [ReturnRaw] in 3.0 (1998)
[LOOKUP] (1997)
Where is f2? (1997)
[WebDNA] triggers executed at boot instead of scheduled time (2011)
DON'T use old cart file! (1997)
sendmail spaces (1997)
Re(2): Share Bulletin Board? (1998)
math with multiple [founditems] (1999)
[OT] Boredom (was: Search Engine Tips) (2003)
[WebDNA] XML error? (2015)
Sort Order on a page search (1997)
Almost a there but..bye bye NetCloak (1997)