Subject | Re: AW: [firebird-support] Embedded and Forced Writes |
---|---|
Author | Ray Cote |
Post date | 2005-02-19T14:49:49Z |
At 12:33 PM +0100 2/19/05, Steffen Heil wrote:
the Windows Explorer.
Bring up a command line while you're writing a large amount of data
to the database and just keep doing "dir" commands. The file rarely
grows -- and the date does not update either.
I also spent a long time looking at this when first using embedded.
Try this experiment:
1: Start writing to the database.
2: Bring up the Windows monitoring tools and watch the disk activity.
You'll see things are being written to the disk.
3: Stop writing to the database.
4: Now disconnect.
You will probably see some disk activity -- but very little.
This is how I finally convinced myself that things were working properly.
--Ray
--
Raymond Cote
Appropriate Solutions, Inc.
PO Box 458 ~ Peterborough, NH 03458-0458
Phone: 603.924.6079 ~ Fax: 603.924.8668
rgacote(at)AppropriateSolutions.com
www.AppropriateSolutions.com
> > AFAIK this is a "feature" of Windows. You dont get fullThis Windows feature is even more disturbing than just not updating
>> details about a file until it has been closed. Watch your
>> disk space and I think you will see it change accordingly.
>> Same thing happens whether you use embedded or not.
>
>afaIk, this is the explorer notification only. The windows explorer updates
>file size display upon change notification.
>However, image a programm that writes 1 byte at a time, 1mb per second.
>Windows would have a lot to do to keep updates on the file size display.
>Therefor notifications are only send when the file handle is closed.
the Windows Explorer.
Bring up a command line while you're writing a large amount of data
to the database and just keep doing "dir" commands. The file rarely
grows -- and the date does not update either.
I also spent a long time looking at this when first using embedded.
Try this experiment:
1: Start writing to the database.
2: Bring up the Windows monitoring tools and watch the disk activity.
You'll see things are being written to the disk.
3: Stop writing to the database.
4: Now disconnect.
You will probably see some disk activity -- but very little.
This is how I finally convinced myself that things were working properly.
--Ray
--
Raymond Cote
Appropriate Solutions, Inc.
PO Box 458 ~ Peterborough, NH 03458-0458
Phone: 603.924.6079 ~ Fax: 603.924.8668
rgacote(at)AppropriateSolutions.com
www.AppropriateSolutions.com