Thanks for the responses. I should give more context.
I was in the process of tracking down how some data files our
applications use became so fragmented. We use Windows 2003 server,
and have not historically used de-fragmenting software (although we
have now started to do so). We had
I have noticed that swap file writes are done in 4K blocks, but file
reads are done in 64K blocks. If it isn't possible to adjust this
behavior with configuration, then I suggest opening this up as a
performance issue that could be addressed in future releases of gvim?
Opening a large file would
skelker wrote:
I have noticed that swap file writes are done in 4K blocks, but file
reads are done in 64K blocks. If it isn't possible to adjust this
behavior with configuration, then I suggest opening this up as a
performance issue that could be addressed in future releases of gvim?
Opening
On Dec 4, 2007 5:40 PM, Tony Mechelynck [EMAIL PROTECTED] wrote:
skelker wrote:
I have noticed that swap file writes are done in 4K blocks, but file
reads are done in 64K blocks. If it isn't possible to adjust this
behavior with configuration, then I suggest opening this up
On Dec 4, 2007 7:40 PM, Tony Mechelynck [EMAIL PROTECTED] wrote:
Regardless, I wonder how much of an issue this really is. It seems to
me that the code is quite optimized
How much of an issue the size of the writes, that is.
[1] fsync is a slow operation, especially on a reiser4
