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

This WebDNA talk-list message is from

2010


It keeps the original formatting.
numero = 105337
interpreted = N
texte = --Apple-Mail-1--189859493 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Simple test, nothing else running on this development server. I have a = page called "autocommit.dna" that contains only the following code, and = a database in the same folder called "autocommit.db" with the fields = indicated in the code comments: [!] autocommit.db: onetwothreefourfivesixseveneightnine= ten [/!] AutoCommit Preference: [lookup db=3Dwebcatalog = prefs&lookinfield=3Dpreference&value=3DAutoCommit&returnfield=3Dvalue]
= [text]tStart=3D[elapsedtime][/text] [text]tLoops=3D10[/text] [loop start=3D1&end=3D[tLoops]] [append = db=3Dautocommit.db]one=3D[index]&two=3D[math][index]*2[/math]&three=3D[mat= h][index]*3[/math]&four=3D[math][index]*4[/math]&five=3D[math][index]*5[/m= ath]&six=3D[math][index]*6[/math]&seven=3D[math][index]*7[/math]&eight=3D[= math][index]*8[/math]&nine=3D[math][index]*9[/math]&ten=3DThis is just = some dummy text.[/append] autocommit.db size: [fileinfo autocommit.db][size]
[/fileinfo] [/loop] Elapsed: [math][elapsedtime]-[tStart][/math] for [tLoops] loops.
When I load the page, I get the following results: AutoCommit Preference: F autocommit.db size: 1213 autocommit.db size: 1267 autocommit.db size: 1322 autocommit.db size: 1378 autocommit.db size: 1435 autocommit.db size: 1492 autocommit.db size: 1549 autocommit.db size: 1606 autocommit.db size: 1663 autocommit.db size: 1721 Elapsed: 0 for 10 loops. As you can see, autocommit is off, and yet the database file on disk = grows after every append. WebDNA has been restarted, so the preference = certainly should be active. Can someone please try this on their server to verify my results? Thanks, Brian Fries BrainScan Software On Jun 14, 2010, at 8:25 PM, Donovan Brooke wrote: > 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 >=20 >=20 >=20 > It takes just a simple test... Brian's comments are spot on (as = usual). >=20 > I am not saying for sure there is a bug.. but from the description: >=20 > -------------------- > Commit Databases: >=20 > 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. > -------------------- >=20 > It appears as if there could be. >=20 > 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? >=20 > 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. >=20 > Donovan >=20 >=20 >=20 >=20 >=20 >=20 > --=20 > Donovan Brooke > Euca Design Center > [Practical-Ethical-Efficient] > www.euca.us > egg.bz > artglass-forum.com > --------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list . > To unsubscribe, E-mail to: > archives: http://mail.webdna.us/list/talk@webdna.us > old archives: http://dev.webdna.us/TalkListArchive/ > Bug Reporting: = http://forum.webdna.us/eucabb.html?page=3Dtopics&category=3D288 --Apple-Mail-1--189859493 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii Simple test, nothing else running on this development server. I have a = page called "autocommit.dna" that contains only the following code, and = a database in the same folder called "autocommit.db" with the fields = indicated in the code comments:


<!--HAS_WEBDNA_TAGS--> [!] autocommit.db: onetwothreefourfivesixseveneightnine= ten [/!] AutoCommit Preference: [lookup db=3Dwebcatalog = prefs&lookinfield=3Dpreference&value=3DAutoCommit&returnfield=3D= value]<br> [text]tStart=3D[elapsedtime][/text] [text]tLoops=3D10[/text] [loop start=3D1&end=3D[tLoops]] [append = db=3Dautocommit.db]one=3D[index]&two=3D[math][index]*2[/math]&thre= e=3D[math][index]*3[/math]&four=3D[math][index]*4[/math]&five=3D[m= ath][index]*5[/math]&six=3D[math][index]*6[/math]&seven=3D[math][i= ndex]*7[/math]&eight=3D[math][index]*8[/math]&nine=3D[math][index]= *9[/math]&ten=3DThis is just some dummy text.[/append] autocommit.db size: [fileinfo autocommit.db][size]<br>[/fileinfo] [/loop] Elapsed: [math][elapsedtime]-[tStart][/math] for [tLoops] = loops.<br>


When I = load the page, I get the following = results:

AutoCommit Preference: = F
autocommit.db size: = 1213
autocommit.db size: = 1267
autocommit.db size: = 1322
autocommit.db size: = 1378
autocommit.db size: = 1435
autocommit.db size: = 1492
autocommit.db size: = 1549
autocommit.db size: = 1606
autocommit.db size: = 1663
autocommit.db size: = 1721
Elapsed: 0 for 10 = loops.

As = you can see, autocommit is off, and yet the database file on disk grows = after every append. WebDNA has been restarted, so the preference = certainly should be active.

Can someone please try this on = their server to verify my results?

Thanks,

Brian = Fries
BrainScan Software

On Jun 14, 2010, at 8:25 PM, Donovan Brooke = wrote:

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.co= m
---------------------------------------------------------
This = message is sent to you because you are subscribed to
the mailing list = <talk@webdna.us>.
To unsubscribe, E-mail to: = <talk-leave@webdna.us>
archives: = http://mail.webdna.us/list/talk@webdna.us
old archives: = http://dev.webdna.us/TalkListArchive/
Bug Reporting: = http://forum.webdna.us/eucabb.html?page=3Dtopics&category=3D288

= --Apple-Mail-1--189859493-- 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)
--Apple-Mail-1--189859493 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Simple test, nothing else running on this development server. I have a = page called "autocommit.dna" that contains only the following code, and = a database in the same folder called "autocommit.db" with the fields = indicated in the code comments: [!] autocommit.db: onetwothreefourfivesixseveneightnine= ten [/!] AutoCommit Preference: [lookup db=3Dwebcatalog = prefs&lookinfield=3Dpreference&value=3DAutoCommit&returnfield=3Dvalue]
= [text]tStart=3D[elapsedtime][/text] [text]tLoops=3D10[/text] [loop start=3D1&end=3D[tLoops]] [append = db=3Dautocommit.db]one=3D[index]&two=3D[math][index]*2[/math]&three=3D[mat= h][index]*3[/math]&four=3D[math][index]*4[/math]&five=3D[math][index]*5[/m= ath]&six=3D[math][index]*6[/math]&seven=3D[math][index]*7[/math]&eight=3D[= math][index]*8[/math]&nine=3D[math][index]*9[/math]&ten=3DThis is just = some dummy text.[/append] autocommit.db size: [fileinfo autocommit.db][size]
[/fileinfo] [/loop] Elapsed: [math][elapsedtime]-[tStart][/math] for [tLoops] loops.
When I load the page, I get the following results: AutoCommit Preference: F autocommit.db size: 1213 autocommit.db size: 1267 autocommit.db size: 1322 autocommit.db size: 1378 autocommit.db size: 1435 autocommit.db size: 1492 autocommit.db size: 1549 autocommit.db size: 1606 autocommit.db size: 1663 autocommit.db size: 1721 Elapsed: 0 for 10 loops. As you can see, autocommit is off, and yet the database file on disk = grows after every append. WebDNA has been restarted, so the preference = certainly should be active. Can someone please try this on their server to verify my results? Thanks, Brian Fries BrainScan Software On Jun 14, 2010, at 8:25 PM, Donovan Brooke wrote: > 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 >=20 >=20 >=20 > It takes just a simple test... Brian's comments are spot on (as = usual). >=20 > I am not saying for sure there is a bug.. but from the description: >=20 > -------------------- > Commit Databases: >=20 > 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. > -------------------- >=20 > It appears as if there could be. >=20 > 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? >=20 > 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. >=20 > Donovan >=20 >=20 >=20 >=20 >=20 >=20 > --=20 > Donovan Brooke > Euca Design Center > [Practical-Ethical-Efficient] > www.euca.us > egg.bz > artglass-forum.com > --------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list . > To unsubscribe, E-mail to: > archives: http://mail.webdna.us/list/talk@webdna.us > old archives: http://dev.webdna.us/TalkListArchive/ > Bug Reporting: = http://forum.webdna.us/eucabb.html?page=3Dtopics&category=3D288 --Apple-Mail-1--189859493 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii Simple test, nothing else running on this development server. I have a = page called "autocommit.dna" that contains only the following code, and = a database in the same folder called "autocommit.db" with the fields = indicated in the code comments:


<!--HAS_WEBDNA_TAGS--> [!] autocommit.db: onetwothreefourfivesixseveneightnine= ten [/!] AutoCommit Preference: [lookup db=3Dwebcatalog = prefs&lookinfield=3Dpreference&value=3DAutoCommit&returnfield=3D= value]<br> [text]tStart=3D[elapsedtime][/text] [text]tLoops=3D10[/text] [loop start=3D1&end=3D[tLoops]] [append = db=3Dautocommit.db]one=3D[index]&two=3D[math][index]*2[/math]&thre= e=3D[math][index]*3[/math]&four=3D[math][index]*4[/math]&five=3D[m= ath][index]*5[/math]&six=3D[math][index]*6[/math]&seven=3D[math][i= ndex]*7[/math]&eight=3D[math][index]*8[/math]&nine=3D[math][index]= *9[/math]&ten=3DThis is just some dummy text.[/append] autocommit.db size: [fileinfo autocommit.db][size]<br>[/fileinfo] [/loop] Elapsed: [math][elapsedtime]-[tStart][/math] for [tLoops] = loops.<br>


When I = load the page, I get the following = results:

AutoCommit Preference: = F
autocommit.db size: = 1213
autocommit.db size: = 1267
autocommit.db size: = 1322
autocommit.db size: = 1378
autocommit.db size: = 1435
autocommit.db size: = 1492
autocommit.db size: = 1549
autocommit.db size: = 1606
autocommit.db size: = 1663
autocommit.db size: = 1721
Elapsed: 0 for 10 = loops.

As = you can see, autocommit is off, and yet the database file on disk grows = after every append. WebDNA has been restarted, so the preference = certainly should be active.

Can someone please try this on = their server to verify my results?

Thanks,

Brian = Fries
BrainScan Software

On Jun 14, 2010, at 8:25 PM, Donovan Brooke = wrote:

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.co= m
---------------------------------------------------------
This = message is sent to you because you are subscribed to
the mailing list = <talk@webdna.us>.
To unsubscribe, E-mail to: = <talk-leave@webdna.us>
archives: = http://mail.webdna.us/list/talk@webdna.us
old archives: = http://dev.webdna.us/TalkListArchive/
Bug Reporting: = http://forum.webdna.us/eucabb.html?page=3Dtopics&category=3D288

= --Apple-Mail-1--189859493-- Brian Fries

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:

Who needs Yoda! (2002) Need help with emailer- 2 issues (1997) [Semi-OT] Eaaaaaasy OSX FTP (2003) [WriteFile] problems (1997) cart info (1998) Permissions / Restart WebDNA? (2005) $append (1998) Rhapsody? (1997) Undeliverable Mail (1997) Location of Browser Info.txt file (1997) Summary search -- speed (1997) anyone moved to v6? (2004) More on the email templates (1997) WebCat2: Items xx to xx shown, etc. (1997) Uh...can someone help me out with the b10? (1997) [SHOWIF AND/OR] (1997) Shopping with Accounts (2003) [WebDNA] test (2013) problems with 2 tags (1997) taxTotal, grandTotal (1997)