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

This WebDNA talk-list message is from

2010

It keeps the original formatting. numero = 105330
interpreted = N
texte = --Apple-Mail-16--238031375Content-Transfer-Encoding: quoted-printableContent-Type: text/plain;charset=us-asciiBrianAre 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.RegardsStuart TremainIDFK Web DevelopmentsAUSTRALIAwebdna@idfk.com.auOn 15/06/2010, at 12:21 PM, Brian Fries wrote:> Thanks, Stuart, but I'm afraid you missed my point, which is this:>=20> Even though AutoCommit is disabled in preferences, the database is =still being written to disk after every single Append context.>=20> Brian Fries> BrainScan Software>=20>=20> On Jun 14, 2010, at 5:22 PM, Stuart Tremain wrote:>=20>> Brian>>=20>> The data will go into the db but the db will not be written to the HD =- if you have a crash then the data is lost.>>=20>> Try putting this at the end of the page to ensure that your data is =written to disk.>>=20>> [COMMITDATABASE db=3DFileName]>>=20>> Putting [COMMITDATABASE db=3DFileName] in your template causes the =specified database file (or full path) to be written but not closed (so =it will remain in RAM). This is only needed for special cases where you =want to be absolutely certain that a database has been written to disk.>>=20>>=20>>=20>> Regards>>=20>> Stuart Tremain>> IDFK Web Developments>> AUSTRALIA>> webdna@idfk.com.au>>=20>>=20>>=20>>=20>> On 15/06/2010, at 10:16 AM, Brian Fries wrote:>>=20>>> I've been playing with the AutoCommit setting fro my databases. =Historically, I've always kept this on to ensure the integrity of my =data. However, I have an application now that really needs all the speed =it can get, and I'd like to disable AutoCommit.>>>=20>>> When I turn off this setting, the databases are still getting =written to disk after every Append. This is with a simple loop that =generates data and appends it to a database. Each time through the loop, =I use [fileinfo] to check the size of the database, and it increases =every time.>>>=20>>> OS X Server, WebDNA 6.1>>>=20>>> Brian Fries>>> BrainScan Software>>>=20>>>=20>>> --------------------------------------------------------->>> 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(8>>=20>=20--Apple-Mail-16--238031375Content-Transfer-Encoding: quoted-printableContent-Type: text/html;charset=us-asciiBrian

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

IDFK Web Developments

AUSTRALIA

webdna@idfk.com.au

On 15/06/2010, at 12:21 PM, Brian Fries wrote:

Thanks, Stuart, but I'm afraid =you missed my point, which is this:

Even though =AutoCommit is disabled in preferences, the database is still being =written to disk after every single Append context.

Brian Fries
BrainScan Software

On Jun 14, 2010, at 5:22 PM, Stuart Tremain =wrote:

Brian

The data will go into the db but the db will =not be written to the HD - if you have a crash then the data is =lost.

Try putting this at the end of the page =to ensure that your data is written to =disk.

[COMMITDATABASE db=3DFileName]
Putting =[COMMITDATABASE db=3DFileName] in your template causes the specified =database file (or full path) to be written but not closed (so it will =remain in RAM). This is only needed for special cases where you want to =be absolutely certain that a database has been written to =disk.

Regards

Stuart =Tremain
IDFK Web Developments
AUSTRALIA
webdna@idfk.com.au

On 15/06/2010, at 10:16 AM, Brian Fries wrote:

I've =been playing with the AutoCommit setting fro my databases. Historically, =I've always kept this on to ensure the integrity of my data. However, I =have an application now that really needs all the speed it can get, and =I'd like to disable AutoCommit.

When I turn off this setting, the =databases are still getting written to disk after every Append. This is =with a simple loop that generates data and appends it to a database. =Each time through the loop, I use [fileinfo] to check the size of the =database, and it increases every time.

OS X Server, WebDNA =6.1

Brian Fries
BrainScan =Software

------------------------------------------------------=---
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>
archi=ves: http://mail.webdna.us/l=ist/talk@webdna.us
old archives: http://dev.webdna.us/TalkLi=stArchive/
Bug Reporting: htt=p://forum.webdna.us/eucabb.html?page=3Dtopics&category(8
=

=--Apple-Mail-16--238031375-- Associated Messages, from the most recent to the oldest:

Re: [WebDNA] Is the AutoCommit preference still supported? (Donovan Brooke 2010)
Re: [WebDNA] Is the AutoCommit preference still supported? (Govinda 2010)
Re: [WebDNA] Is the AutoCommit preference still supported? (Brian Fries 2010)
Re: [WebDNA] Is the AutoCommit preference still supported? (Donovan Brooke 2010)
Re: [WebDNA] Is the AutoCommit preference still supported? (Stuart Tremain 2010)
Re: [WebDNA] Is the AutoCommit preference still supported? (Brian Fries 2010)
Re: [WebDNA] Is the AutoCommit preference still supported? (Stuart Tremain 2010)
[WebDNA] Is the AutoCommit preference still supported? (Brian Fries 2010)

--Apple-Mail-16--238031375Content-Transfer-Encoding: quoted-printableContent-Type: text/plain;charset=us-asciiBrianAre 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.RegardsStuart TremainIDFK Web DevelopmentsAUSTRALIAwebdna@idfk.com.auOn 15/06/2010, at 12:21 PM, Brian Fries wrote:> Thanks, Stuart, but I'm afraid you missed my point, which is this:>=20> Even though AutoCommit is disabled in preferences, the database is =still being written to disk after every single Append context.>=20> Brian Fries> BrainScan Software>=20>=20> On Jun 14, 2010, at 5:22 PM, Stuart Tremain wrote:>=20>> Brian>>=20>> The data will go into the db but the db will not be written to the HD =- if you have a crash then the data is lost.>>=20>> Try putting this at the end of the page to ensure that your data is =written to disk.>>=20>> [COMMITDATABASE db=3DFileName]>>=20>> Putting [COMMITDATABASE db=3DFileName] in your template causes the =specified database file (or full path) to be written but not closed (so =it will remain in RAM). This is only needed for special cases where you =want to be absolutely certain that a database has been written to disk.>>=20>>=20>>=20>> Regards>>=20>> Stuart Tremain>> IDFK Web Developments>> AUSTRALIA>> webdna@idfk.com.au>>=20>>=20>>=20>>=20>> On 15/06/2010, at 10:16 AM, Brian Fries wrote:>>=20>>> I've been playing with the AutoCommit setting fro my databases. =Historically, I've always kept this on to ensure the integrity of my =data. However, I have an application now that really needs all the speed =it can get, and I'd like to disable AutoCommit.>>>=20>>> When I turn off this setting, the databases are still getting =written to disk after every Append. This is with a simple loop that =generates data and appends it to a database. Each time through the loop, =I use [fileinfo] to check the size of the database, and it increases =every time.>>>=20>>> OS X Server, WebDNA 6.1>>>=20>>> Brian Fries>>> BrainScan Software>>>=20>>>=20>>> --------------------------------------------------------->>> 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(8>>=20>=20--Apple-Mail-16--238031375Content-Transfer-Encoding: quoted-printableContent-Type: text/html;charset=us-asciiBrian