So would a FlushDatabases, =which I understand is All DB Written to Disk be a "slower" task compared =to a [commitdatabas....] after every [replace/append] =?
I would assume that flushing all databases to =disk would be slower. About [FLUSHDATABASES] the manual says it, ="causes all databases to be written and closed". Why would =you want to *close* the database just to make sure the data is on disk? = Then upon the very next operation that involves that =database, you have to load it all back into RAM again. I =would not close the database (remove it from RAM) unless there was a =reason to do so. I would also not commit to disk, nor remove from =RAM, ALL databases at once, unless there was a reason to do so. =
[COMMITDATABASE..] lets you precisely write to disk (but =not flush from RAM) *just the database you specify*.And how do you =normally avoid data loss? Are you using the [commitdatabase...] =??
Well my clients are all over the map.. on =different hosts, etc. Some have auto-commit turned on via =the admin interface.. Other times/places I do use =[commitdatabase...], specifically, when/where =needed.
-G---------------------------------------------------------=
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
Bug Reporting: support@webdna.us
|
So would a FlushDatabases, =which I understand is All DB Written to Disk be a "slower" task compared =to a [commitdatabas....] after every [replace/append] =?
I would assume that flushing all databases to =disk would be slower. About [flushdatabases] the manual says it, ="causes all databases to be written and closed". Why would =you want to *close* the database just to make sure the data is on disk? = Then upon the very next operation that involves that =database, you have to load it all back into RAM again. I =would not close the database (remove it from RAM) unless there was a =reason to do so. I would also not commit to disk, nor remove from =RAM, ALL databases at once, unless there was a reason to do so. =
[COMMITDATABASE..] lets you precisely write to disk (but =not flush from RAM) *just the database you specify*.And how do you =normally avoid data loss? Are you using the [commitdatabase...] =??
Well my clients are all over the map.. on =different hosts, etc. Some have auto-commit turned on via =the admin interface.. Other times/places I do use =[commitdatabase...], specifically, when/where =needed.
-G---------------------------------------------------------=
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
Bug Reporting: support@webdna.us
DOWNLOAD WEBDNA NOW!
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...