Re: AutoCommit Preference?
This WebDNA talk-list message is from 1998
It keeps the original formatting.
numero = 16464
interpreted = N
texte = >>What triggers this auto-commit activity that makes it slower when it's On than when it's Off? > >If any databases are dirty after the page is returned, they are written to disk. That takes some time, but is of course safer if you have an unstable server. > >>Is it triggered every time a page is requested? > >Yes, but if no databases are dirty, then there is no slowdown.All I was trying to figure out is whether or not having the AutoCommit set to T is going to make WebCat slower than if I continued to use [closedatabase] tags after all my replace and delete commands, like I've been doing all along.From what you're telling me, it seems like using AutoCommit would be even faster than using [closedatabase] tags -- because the [closedatabase] tag actually purges the data from RAM in addition to writing the data to disk, which means using the [closedatabase] tag will always require reloading of the data from disk the next time the db is called.So *assuming* that the AutoCommit checking does NOT slow down the server when the db's are clean, using the new AutoCommit feature would actually be FASTER than using [closedatabase] tags, right? Ah, but how would this compare with using [commitdatabase] tags instead of [closedatabase] tags?Will setting AutoCommit to T be faster than setting it to F and using [commitdatabase] tags after replace and delete commands?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:
>>What
triggers this auto-commit activity that makes it slower when it's On than when it's Off? > >If any databases are dirty after the page is returned, they are written to disk. That takes some time, but is of course safer if you have an unstable server. > >>Is it triggered every time a page is requested? > >Yes, but if no databases are dirty, then there is no slowdown.All I was trying to figure out is whether or not having the AutoCommit set to T is going to make WebCat slower than if I continued to use
[closedatabase] tags after all my replace and delete commands, like I've been doing all along.From what you're telling me, it seems like using AutoCommit would be even faster than using
[closedatabase] tags -- because the
[closedatabase] tag actually purges the data from RAM in addition to writing the data to disk, which means using the
[closedatabase] tag will always require reloading of the data from disk the next time the db is called.So *assuming* that the AutoCommit checking does NOT slow down the server when the db's are clean, using the new AutoCommit feature would actually be FASTER than using
[closedatabase] tags, right? Ah, but how would this compare with using
[commitdatabase] tags instead of
[closedatabase] tags?Will setting AutoCommit to T be faster than setting it to F and using
[commitdatabase] tags after replace and delete commands?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:
emailer (1997)
WebCat2b15MacPlugin - showing [math] (1997)
Up and running ... at last !! (1997)
Plugin causes type 2 error on WebStar startup (2000)
Comments in db? (1997)
Sandbox Prefs (2003)
WebCat2 - Getting to the browser's username/password data (1997)
Statistics... (2004)
Re:I've had it! (1999)
Email Formatting and Encryption (1998)
PCS Frames (1997)
Re(2): Append command (1999)
"Advanced" Search Algorithm (2008)
Forms IMG tag[OT] (2001)
RE: Cart Template (1997)
Instructions for Digest (1997)
Announce: New WebCatalog Site (1998)
Where is f2? (1997)
price totals (2003)
WC Database Format (1997)