On 17/07/2013 17:13, Benjamin Fritz wrote:
On Wed, Jul 17, 2013 at 10:49 AM, Mike Williams
<[email protected]> wrote:
Does anyone have hard numbers? I have just loaded an ~900MB PDF file in ~7s
(Win7 x64, 8GB, Core2Duo 2.3GHz), my normal VIM config (although I do have
maxmem always set to maximum).
Now try writing it. I suppose if Vim is only being used as a viewer
this might be a non-issue, but I discovered the problem when trying to
create a file with a huge number of lines to test how Vim responded
to...something. I don't exactly remember what I was trying to test,
only that I gave up on having Vim create the file and instead did it
using command-line tools (a huge pain on Windows), and then eventually
gave up on testing in general because Vim was taking so long to
manipulate the file.
Elapsed time is ~30s. Putting a profiler on VIM while it was writing
the file it reported around ~5s CPU time driving the write to disk - the
rest of it is waiting for file IO to complete. So both reading and
writing of large files is (not too surprisingly) IO bound and dependent
on OS behaviour and current system usage (available memory for file
cache, paging other apps and data out as required, etc.)
The solution for handling this is a concurrent reading/writing threads
with some new and interesting problems dealing with editing before the
concurrent activities have finished. Given how atypical this issue is I
would think there is not a great push to improve things.
First time to load the file took an age
(>40s) due to loading it off disk
That sounds about right. Or maybe longer.
Cold file caches are a pain in the a**e! ;-)
- once it is in the OS file cache
restarting vim to read the file was quick (I'd expect some delay with such a
large file). Is this the sort of pattern you are seeing?
I don't recall.
Mike
--
EXPERIENCE - experience is a wonderful thing. It enables you to
recognise a mistake when you make it again.
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
