On Wednesday, July 17, 2013 11:54:59 AM UTC-5, Mike Williams wrote: > 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.
That's not what I saw. I let Vim run after doing :w for several minutes, and then force-killed it. My file was millions of very small lines (maybe empty, I don't remember). I don't plan on trying again for now. -- -- 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.
