Hi! Dominik wrote:
> after some more tests I found out that the caching is enabled for > exporting. :-( That's hard to turn off. You have to call fsync()/fdatasync() before each posix_fadvise() if you want to really remove the output file's pages from the cache. Unfortunately, that's a synchronous operation: it will not return until all data has been written to disk. Therefore, it may add a lot of additional delay. > That means for users with 3,6GB free mem: (and enabled caching during > import) > - videos till 1,8 GB: max speed at exporting (mem->disk) > - videos from 1,8GB till 3,6GB: more or less performance boost at > exporting (at the beginning it's a mem->disk later disk->disk) Actually, that depends on the cache. > - videos above 3,6 GB: no performance advantage or disadvantage, just > like pure disk->disk export as today Only if dvbcut is the only application running. [...] > What do you think of the proposal? If you absolutely want a resource hog, I can add a command line option that enables input caching. I don't think it's a good idea to put it in the configuration file, though. -- Michael "Tired" Riepe <[EMAIL PROTECTED]> X-Tired: Each morning I get up I die a little ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ DVBCUT-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dvbcut-user
