Started by smartbit, January 27, 2014, 10:27:16 AM
Quote from: edkiefer on February 04, 2014, 07:11:25 AMOne thing is to limit log writes , I always disable log processes launches and terminations , I don't need that option on ,except for debugging some issue .Those two will stop 80% of logs ,unless you have a lot of rules setup .
Quote from: smartbit on February 04, 2014, 07:17:54 AMP.S. - BenYeeHua, the fragmentation I'm talking about IS the disk fragmentation, and I'm aware of the fact that updating (increasing the size, precisely) of the files will cause fragmentation. Also, it's not completely true that it's impossible to force windows to save continuous space. It can be done by allocating space for a specific file size, and creating this file in advance. Modifying its contents later as much as you wish, as long as you fit inside the original boundaries. (It is (partially) similar to the way Page File being handled. And many other programs use this technique.)But doing it here, may need some redesign of the current mechanisms here, and will cause too much trouble to go through for a not-so-important reason. Thats why I'm asking about a possibility to optionally decrease write frequency by more minor SW modifications.
Quote from: BenYeeHua on February 04, 2014, 12:53:04 PM... so if you want 1-2 MB delayed write, I think it need system to buffering 4-8 hours ...
Quote from: smartbit on February 04, 2014, 06:09:51 PMI gave 1-2 MB just as an example to point that the cache size is not the issue here. There is no reason for actually caching for so long with Process Lasso. Buffering for a several minutes should be sufficient. And compared to the way it works now (few writes per minute) it should show a good improvement.
Quote from: BenYeeHua on February 05, 2014, 02:27:32 AMRoger, but the file is using FILE_ATTRIBUTE_TEMPORARY, like what's you found.So I guess you always don't has enough available memory to buffering the file, and causing it write each minute, or it is a bug/design for windows?
QuoteSpecifying the FILE_ATTRIBUTE_TEMPORARY attribute causes file systems to avoid writing data back to mass storage if sufficient cache memory is available, because an application deletes a temporary file after a handle is closed. In that case, the system can entirely avoid writing the data. Although it does not directly control data caching in the same way as the previously mentioned flags, the FILE_ATTRIBUTE_TEMPORARY attribute does tell the system to hold as much as possible in the system cache without writing and therefore may be of concern for certain applications.