Writing Record to File without the Delay Time

Question

2.50/5 (2 votes)

See more:

Is there a way/process to eliminate the delay when writing a record to a file. I am wirting records to a file but when it is interrupted (unknown cause, user ended it, etc) it will sometimes not write the records to the file.

Posted 23-Jul-14 10:14am

CaptainJack683

Add a Solution

Comments

Kornfeld Eliyahu Peter 23-Jul-14 16:15pm

Write without buffering...

Sergey Alexandrovich Kryukov 23-Jul-14 17:01pm

The question as you formulated it does not really make sense. You need to clarify it.
—SA

2 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

CaptainJack683 · Answer 1 · 2014-07-24T11:19:00

you would use the autoflush = true within streamwriter or streamwriter.flush() after each writeline.

using (StreamWriter outStream = new StreamWriter(fromPath + outFileName + fileSuffix))
{
// set the writing file to be auto-flushed so as each line gets written right away.
outStream.AutoFlush = true;
//
// ... program stream here
//
outStream.WriteLine(strText);
}

Matt T Heffron · Answer 2 · 2014-07-23T10:27:00

Solution 1

"I cannot change the laws of physics!" - Scotty, "The Naked Time" -1966

It takes time to do everything.
Open the file,
load the data (to a buffer) from the disk for the sector(s) containing the location where the new record will be written,
transfer the new record data to the buffer,
write the buffer back to the disk,
close the file (updating the file modification time stamp, disk allocation tables, etc.)

The system can be interrupted at any point above and there's no way to recover.

Posted 23-Jul-14 10:27am

Matt T Heffron

Comments

Sergey Alexandrovich Kryukov 23-Jul-14 17:00pm

You are right, but I feel the user means something different, like aborting the operation by other thread or something like that. Perhaps OP tried to make the thread abortable by adding some artificial Thread.Sleep operations, spin wait. I say so because I know some typical mistakes of the developers. With the information OP provided, it's nearly impossible to give a satisfactory answer. We would need some OP's clarification.
—SA

CaptainJack683 24-Jul-14 16:14pm

But after program has written 10 or so data records to buffer/file should they not be written on the actual file.

Matt T Heffron 24-Jul-14 17:43pm

Not unless you force the buffer to be flushed, as you noted in your "Solution".
The OS is free to keep buffers un-flushed pretty much as long as it wants until told otherwise.