Re: Temp DB (Was freeze)

This WebDNA talk-list message is from

2003


It keeps the original formatting.
numero = 47647
interpreted = N
texte = On 2/10/03 10:18 PM, Kenneth Grome wrote:>> Unless I am missing something, how did you make the leap to this happening >> on every append, replace or delete. Isnt this true that unless your prefs >> are set to commit on every change (I don't know of anyone that does that), > > The software's default setting is to commit upon every change. > Therefore, I believe that more users are having their db files > written to disk upon every change than you think. Possibly.> >> this procedure is ONLY going to happen when you tell the app to commit >> (write) the db to disk? > > I don't know if it's true or not. It *should* be, which means you're > right and I'm wrong -- except for the majority of users who don't > change the default preferences because they really don't understand > them. And in that case, since the writing of DBs was happening for them on every change anyway, the loss of performance of a delete/rename is almost certainly a fraction of the time already spent on the File I/O being used to write those poor DBs to the HD every couple of seconds.If anything, _that_ defeats the purpose of a RAM based DB (with the exception of blazing fast searching), yet doesn't significantly change the performance from pre 4.5 versions.Essentially, if they were doing it before, then the impact would seem to be practically irrelevant, and if they were not committing on every change, then the new performance is even less of an issue than the minor one in the worst case above.But again, I have to yield to the knowledge of those who programmed it.AlexAlex J McCombie New World Media Chief Information Officer Drawer 607 800/724.8973 Fair Haven, NY 13064 Alex@NewWorldMedia.com http://OurClients.comInterface Designer WebDNA Programmer Database Designer------------------------------------------------------------- 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:

    
  1. Re: Temp DB (Was freeze) (Alain Russell 2003)
  2. Re: Temp DB (Was freeze) (Alex McCombie 2003)
  3. Re: Temp DB (Was freeze) (John Hill 2003)
  4. Re: Temp DB (Was freeze) (Alain Russell 2003)
  5. Re: Temp DB (Was freeze) (Alex McCombie 2003)
  6. Re: Temp DB (Was freeze) (Alex McCombie 2003)
  7. Re: Temp DB (Was freeze) (John Hill 2003)
  8. Re: Temp DB (Was freeze) (Kenneth Grome 2003)
  9. Temp DB (Was freeze) (Alex McCombie 2003)
On 2/10/03 10:18 PM, Kenneth Grome wrote:>> Unless I am missing something, how did you make the leap to this happening >> on every append, replace or delete. Isnt this true that unless your prefs >> are set to commit on every change (I don't know of anyone that does that), > > The software's default setting is to commit upon every change. > Therefore, I believe that more users are having their db files > written to disk upon every change than you think. Possibly.> >> this procedure is ONLY going to happen when you tell the app to commit >> (write) the db to disk? > > I don't know if it's true or not. It *should* be, which means you're > right and I'm wrong -- except for the majority of users who don't > change the default preferences because they really don't understand > them. And in that case, since the writing of DBs was happening for them on every change anyway, the loss of performance of a delete/rename is almost certainly a fraction of the time already spent on the File I/O being used to write those poor DBs to the HD every couple of seconds.If anything, _that_ defeats the purpose of a RAM based DB (with the exception of blazing fast searching), yet doesn't significantly change the performance from pre 4.5 versions.Essentially, if they were doing it before, then the impact would seem to be practically irrelevant, and if they were not committing on every change, then the new performance is even less of an issue than the minor one in the worst case above.But again, I have to yield to the knowledge of those who programmed it.AlexAlex J McCombie New World Media Chief Information Officer Drawer 607 800/724.8973 Fair Haven, NY 13064 Alex@NewWorldMedia.com http://OurClients.comInterface Designer WebDNA Programmer Database Designer------------------------------------------------------------- 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/ Alex McCombie

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:

building / customizing stores (2000) Almost a there but..bye bye NetCloak (1997) Optimized (2000) Superfilous Characters (1998) web delivery (1997) SQL / Webcat Help (1999) shipping calcs (1998) FlushDatabase Suggestion (1998) WebCatalog for Postcards ? (1997) Re[2]: 2nd WebCatalog2 Feature Request (1996) RE: File Uploads: WebCat/SiteEdit (1998) WebTen and WebCat (1997) filemaker - orderfile (1997) [SubTotal] again (1998) [ConvertChars] problem (1997) SSL and reg web*L and reg web* (1997) still having shipCost.db Problem (1997) How true is this? (1999) [WebDNA] How is Webdna talking with Postfix? (2015) Choices (2000)