On Friday, June 1, 2012 5:07:38 PM UTC-5, Shawn wrote: > Hello, > > I have used vim for several years now, but recently vim has become > painfully slow when it writes to disk. I am checking into other > possibilities, but one reason for this (in my mind) might be that I > have too many instances of vim up at the same time. I have 48 GB of > memory, so I don't think that it is a memory issue, and my files are > relatively small (~500 lines), so I am wondering if there is some > central vim manager that gets overworked if I keep pulling up vim > instances and not closing the others. Does this make sense? If so, > is there anything I can do about it other than closing the files that > I am keeping up? If not, any other ideas as to why it might be so > slow? I just saved a 650 line file, it took 34 seconds.
Nope, no central Vim manager, they're all independent unless you explicitly make them communicate. Do operations outside of Vim take a long time as well, or just Vim? Can you reproduce it without all your personal config and plugins, too? It's possible one of those is interfering. I have noticed that Vim can be VERY slow if runtimepath contains network directories...I've moved my config files to my local disk to fix that. Or maybe you're saving a really huge .viminfo and/or undo file along with the file you're saving? Note Vim comes with profiling features, depending on what options you compiled with. See :help profile. You may be able to find the culprit using that, but then again, maybe not. -- You received this message from the "vim_use" 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
