Re: [WebDNA] Is the AutoCommit preference still supported?

This WebDNA talk-list message is from

2010


It keeps the original formatting.
numero = 105331
interpreted = N
texte = Stuart Tremain wrote: > Brian > > Are you sure about that ? > > I am under the impression that WebDNA does not write the db to disk > unless it is instructed OR you have AutoCommit on OR RAM is full and it > needs to close the DB therefore writing it to disk. > > Are you saying that even though you have AUTOCOMMIT off it is still > writing to disk ? > > Have you tried restarting WebDNA to ensure that the new prefs are being > used not the old ones being cached ? > > Maybe you have a RAM vs DB size issue and it is being written to disk > because it is taking up too much RAM ? > > Other dbs on the server may also be forcing this issue. > > Regards > > Stuart Tremain It takes just a simple test... Brian's comments are spot on (as usual). I am not saying for sure there is a bug.. but from the description: -------------------- Commit Databases: Causes database files to be written to disk immediately after modification, rather than waiting until they are closed. Can improve reliability if your server ever crashes before writing databases to disk, but slows down the server overall if you have lots of database modifications. -------------------- It appears as if there could be. It is indeed the case that WebDNA is writing to disk seemingly instantly in my tests with that setting either on or off. My next test would be to do the same tests on a server that is being hit harder than my dev machine (which I don't have time to do).. the theory being perhaps it's a priority thing? At any rate, if I were Chris, I'd put this on the list to be looked at by Jaz to find out exactly what is going on and what was intended with that setting. Donovan -- Donovan Brooke Euca Design Center [Practical-Ethical-Efficient] www.euca.us egg.bz artglass-forum.com Associated Messages, from the most recent to the oldest:

    
  1. Re: [WebDNA] Is the AutoCommit preference still supported? (Donovan Brooke 2010)
  2. Re: [WebDNA] Is the AutoCommit preference still supported? (Govinda 2010)
  3. Re: [WebDNA] Is the AutoCommit preference still supported? (Brian Fries 2010)
  4. Re: [WebDNA] Is the AutoCommit preference still supported? (Donovan Brooke 2010)
  5. Re: [WebDNA] Is the AutoCommit preference still supported? (Stuart Tremain 2010)
  6. Re: [WebDNA] Is the AutoCommit preference still supported? (Brian Fries 2010)
  7. Re: [WebDNA] Is the AutoCommit preference still supported? (Stuart Tremain 2010)
  8. [WebDNA] Is the AutoCommit preference still supported? (Brian Fries 2010)
Stuart Tremain wrote: > Brian > > Are you sure about that ? > > I am under the impression that WebDNA does not write the db to disk > unless it is instructed OR you have AutoCommit on OR RAM is full and it > needs to close the DB therefore writing it to disk. > > Are you saying that even though you have AUTOCOMMIT off it is still > writing to disk ? > > Have you tried restarting WebDNA to ensure that the new prefs are being > used not the old ones being cached ? > > Maybe you have a RAM vs DB size issue and it is being written to disk > because it is taking up too much RAM ? > > Other dbs on the server may also be forcing this issue. > > Regards > > Stuart Tremain It takes just a simple test... Brian's comments are spot on (as usual). I am not saying for sure there is a bug.. but from the description: -------------------- Commit Databases: Causes database files to be written to disk immediately after modification, rather than waiting until they are closed. Can improve reliability if your server ever crashes before writing databases to disk, but slows down the server overall if you have lots of database modifications. -------------------- It appears as if there could be. It is indeed the case that WebDNA is writing to disk seemingly instantly in my tests with that setting either on or off. My next test would be to do the same tests on a server that is being hit harder than my dev machine (which I don't have time to do).. the theory being perhaps it's a priority thing? At any rate, if I were Chris, I'd put this on the list to be looked at by Jaz to find out exactly what is going on and what was intended with that setting. Donovan -- Donovan Brooke Euca Design Center [Practical-Ethical-Efficient] www.euca.us egg.bz artglass-forum.com Donovan Brooke

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:

Can I do these? (1997) Limiting user access to .tmpl files (1997) forming a SKU (1999) WebCat2 - Getting to the browser's username/password data (1997) WebCat2 several catalogs? (1997) Wanted: Broader string manipulation functions (1997) Looking up two prices in Formulas.db (1997) RE: storefront (1998) Bug or syntax error on my part? (1997) creating writefile data from a nested search (1997) Questions (1998) [WebDNA] SOAP support (2014) Dates! (1998) Now you see it now you donīt (1997) Forms Search Questions (1997) TCPConnect / Current Temperature (2004) Exclude by date - multiple (1997) Searching multiple fields (1997) Date problems (1997) PR: WebCatalog Affiliates Program Announced -- Share the revenue for promoting WebCatalog (2000)