On Mar 21, 5:48 am, pmehrwald <[email protected]> wrote: > Hi, > > We are facing a severe problem on using :g on our machines at work. On > two different dell machines this command causes problems after > updating to x64 Windows 7 or Windows Server 2008. > > The scenario is as follows: > * Logfile ~100Mb opened > * execute :%g!/xxx/d to remove some lines > * PC is completely blocking for more than 10 minutes. Task Manager is > only updating sometimes and shows 99% CPU for gvim.exe. No other > software can be used at this time. > > This is my PC: > Intel i7 CPU 4x2.80 GHz, Hyper threading activated > 16 Gb Ram > 64bit Windows 7
I find it very strange that you have a 4-CPU system, and yet Vim (a single-threaded application) is able to max out all 4 of them. > > We tried v 7.2, v7.3 for x86 and x64. > > I hope someone can help us...thank you > Philipp Is any syntax highlighting active? Is the log on a network share? Answering "no" to these should also make things faster. In addition to these and Antonio's 'ul' suggestion, you can try turning off swap files, undo files, and a few other things. Actually the LargeFile.vim plugin does a lot of this for you. 100MB is fairly large but Vim should still be able to handle it. -- 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
