This topic is now archived and is closed to further replies.

Optimizing disk reads for raw video.

This topic is 5310 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Recommended Posts

Hey, I''m working on a game, in which I need to display video. For several reasons, the video needs to be in a raw format, and read in at runtime. (Windows) To display, I use a buffer of 20 frames. On initialisation I fill them all. When the game requests a frame from the videomanager, it gets a frame of this buffer (a pointer to it). When the videomanager has given out the first 10 frames, it spawns a new thread, to read in the next 10 frames from disk, and puts it in the first half of the buffer. When the videomanager reaches the end of its buffer, it spawns a new thread to fill the last 10 frames of the buffer. Inside the thread, I use this fread call to get the data, after I''ve set the file to use __IONBF io. (I only set the buffertype once) bytesToRead=640*480*2*10 // 2=16 bits, 10=size of half a buffer // 640x480 is resolution. fread(mybuffer,1,bytesToRead,pFileHandle); I''d be very interested in hearing ideas on optimizing my datareading method, as it is more choppy than I like, and I can''t help the feeling that it can be implemented faster. In order to try to not get multiple threads doing io on the same file at the same time, (in the fear of speed penalties for the harddrive''s seektime), I do not spawn a new readthread untill the old one is ready. (In this case, the videomanager just feeds the game the same image as last time, when the game requests a videoframe) Thanks, Lucas

Share this post

Link to post
Share on other sites
Hey Jan.

Thanks for the tips. I''ve started implementing them yesterday.

I''m now using CreateFile and ReadFileEx for my input and output.
This is my CreateFile call:


Specifying sequential, unbuffered, async io.
It performs much better.

Your third comment I couldn''t find any info on. Is doing a ReadFileEx() a ''deep request'' ? If not, how do I issue one?. In my current implementation, I always make sure the previous ReadFileEx() command has completed before finishing a new one. I''ve tried setting it to allow two simultaneous, but didn''t see a performance difference.



Share this post

Link to post
Share on other sites
Glad it helped.
By ''n deep'' I mean n active requests. I was thinking about optimizing throughput recently, and n=2 is a bit better (the hard drive always has something to do, doesn''t have to wait for requests). In your case, I guess it doesn''t make a difference - you can afford a bit extra latency, because of your buffer.
There is no performance penalty for multiple calls before one completes.

Share this post

Link to post
Share on other sites
And why not directly load a new frame whenever one has been displayed? Something like this:

//pseudo code
int Counter;
MovieFrame FrameBuffer[9];

for (Counter = 0;Counter < 10;Counter ++){
FrameBuffer[Counter] := ReadFrameFromMovie(Counter);
for (Counter = 0;Counter <= (Movie.Length - 10);Counter++){
FrameBuffer[Counter] = ReadFrameFromMovie(Counter + 10);

Oh, did I mention that C(++) is not exactly my strongest language(...)? Anyway, I think the idea should be clear....

Share this post

Link to post
Share on other sites
You might want to consider using compression on the frames. Loading data from disk takes much longer than any average compression algorithm. You would get a very large performance boost.

Share this post

Link to post
Share on other sites
I decided to store the video raw, because in this game, the cpu is extremely busy doing all sorts of stuff, mainly taking the video as input. The CPU is absolutely the bottleneck for me. If I turn off the reading of ''new'' video frames, I have exactly the same fps, as when the hd is loading in the background.

I''ve taken Jan''s suggestions, and switched to CreateFile and ReadFileEx. Then I discovered that win98 doesn''t support overlapped io.. So now I use CreateFile() and ReadFile(), but I have a seperate thread do the blocking ReadFile() call.

The thread that does the reading runs this in its main function:

if (readThreadStop) return 0;
if (bytesRead!=readThreadBytesToRead)
} while (1);

so it sleeps, reads, sleeps reads.. When it sleeps it gets called out of that by the mainthread using QueueUserAPC(), which fills the readThreadBytesToRead and readThreadBuffer with new values.

Problem is that it still crashes on win98. I''m trying to figure out what it is I''m doing that is unsupported on win98. My guess goes out to the QueueuserAPC() call, but MSDN has no mention of that not working on earler windows version..

Any clues?

Bye, Lucas

Share this post

Link to post
Share on other sites