Slow down when typing?
-
(sorry for the cross post, but...) My team is having an odd problem: We are getting severe slowdowns when typing in largeish files: 2, 3 sometimes as long as four seconds when hitting Return. It seems to be limited to fairly large source files (3,000 or more lines, but I haven't narrowed down the threshold yet). And if we close the workspace, then there is no problem at all with performance. Reopen the workspace, and the slowdowns are back. So, it's clearly something in Visual Studio. Some facts about what we're doing: - Our workspace is large with hundreds of .cp files and more than a thousand .h files broken up into "folders" within the workspace. - In fairly large files, typing can be very slow: 2, 3 even four seconds of a "pause" when hitting return - Task Manager does show CPU spikes during this activity - We are running P3 733 dual CPU Compaq AP550 workstations - If we close the workspace, typing performance is normal and does not exhibit the slowdowns - Generate Browse Info is turned off in Project Settings | C++ - Build Browse Info file is turned off in Project Settings | Browse Info - We are no longer using USERTYPE.DAT for user defined keywords, the file does not even exist - We are using SourceSafe for source control, but SourceSafe itself is not open at the time of these slowdowns - All four of the VS "statement completion options" in Options | Editor are off (Auto list members, auto type info, etc.) - The VS "auto indent" feature in Options | Tabs seems to make no difference: we've tried None, Default and Smart - We are using Visual C++ 6.0 SP5 - We are not using any other AddIns other than DevTrueColor to patch the color menus to allow us any color in the syntax color chooser - I've search MSDN and the KB as much as I can, but can't find anything Any ideas would be very much appreciated. -- Bryan
-
(sorry for the cross post, but...) My team is having an odd problem: We are getting severe slowdowns when typing in largeish files: 2, 3 sometimes as long as four seconds when hitting Return. It seems to be limited to fairly large source files (3,000 or more lines, but I haven't narrowed down the threshold yet). And if we close the workspace, then there is no problem at all with performance. Reopen the workspace, and the slowdowns are back. So, it's clearly something in Visual Studio. Some facts about what we're doing: - Our workspace is large with hundreds of .cp files and more than a thousand .h files broken up into "folders" within the workspace. - In fairly large files, typing can be very slow: 2, 3 even four seconds of a "pause" when hitting return - Task Manager does show CPU spikes during this activity - We are running P3 733 dual CPU Compaq AP550 workstations - If we close the workspace, typing performance is normal and does not exhibit the slowdowns - Generate Browse Info is turned off in Project Settings | C++ - Build Browse Info file is turned off in Project Settings | Browse Info - We are no longer using USERTYPE.DAT for user defined keywords, the file does not even exist - We are using SourceSafe for source control, but SourceSafe itself is not open at the time of these slowdowns - All four of the VS "statement completion options" in Options | Editor are off (Auto list members, auto type info, etc.) - The VS "auto indent" feature in Options | Tabs seems to make no difference: we've tried None, Default and Smart - We are using Visual C++ 6.0 SP5 - We are not using any other AddIns other than DevTrueColor to patch the color menus to allow us any color in the syntax color chooser - I've search MSDN and the KB as much as I can, but can't find anything Any ideas would be very much appreciated. -- Bryan
I've seen this - I think it has something to do with the undo functionality, which gets hit hard when you have a lot of files open. Seems to me the .opt file enters into this somewhere, though it may just be a side effect in that it gets larger the more files you have open. Have you tried closing files and/or deleting the .opt file?
-
I've seen this - I think it has something to do with the undo functionality, which gets hit hard when you have a lot of files open. Seems to me the .opt file enters into this somewhere, though it may just be a side effect in that it gets larger the more files you have open. Have you tried closing files and/or deleting the .opt file?
Tim, thanks for the quick response. Unfortunately, I just tried deleting the .opt file and the problem still exists, even with just one file open (and of course the workspace, close the workspace and the problem is gone). We've done clean installs of VC++ on to clean installs of both NT 4 and W2K, no luck. :( -- Bryan
-
Tim, thanks for the quick response. Unfortunately, I just tried deleting the .opt file and the problem still exists, even with just one file open (and of course the workspace, close the workspace and the problem is gone). We've done clean installs of VC++ on to clean installs of both NT 4 and W2K, no luck. :( -- Bryan
Hmmm - might try the .ncb - safe to delete, but not sure its the cause of the problem. Seems to me I was able to speed things up by deleting the opt file...
-
(sorry for the cross post, but...) My team is having an odd problem: We are getting severe slowdowns when typing in largeish files: 2, 3 sometimes as long as four seconds when hitting Return. It seems to be limited to fairly large source files (3,000 or more lines, but I haven't narrowed down the threshold yet). And if we close the workspace, then there is no problem at all with performance. Reopen the workspace, and the slowdowns are back. So, it's clearly something in Visual Studio. Some facts about what we're doing: - Our workspace is large with hundreds of .cp files and more than a thousand .h files broken up into "folders" within the workspace. - In fairly large files, typing can be very slow: 2, 3 even four seconds of a "pause" when hitting return - Task Manager does show CPU spikes during this activity - We are running P3 733 dual CPU Compaq AP550 workstations - If we close the workspace, typing performance is normal and does not exhibit the slowdowns - Generate Browse Info is turned off in Project Settings | C++ - Build Browse Info file is turned off in Project Settings | Browse Info - We are no longer using USERTYPE.DAT for user defined keywords, the file does not even exist - We are using SourceSafe for source control, but SourceSafe itself is not open at the time of these slowdowns - All four of the VS "statement completion options" in Options | Editor are off (Auto list members, auto type info, etc.) - The VS "auto indent" feature in Options | Tabs seems to make no difference: we've tried None, Default and Smart - We are using Visual C++ 6.0 SP5 - We are not using any other AddIns other than DevTrueColor to patch the color menus to allow us any color in the syntax color chooser - I've search MSDN and the KB as much as I can, but can't find anything Any ideas would be very much appreciated. -- Bryan
This has happened to me as well. I still haven't found a solution but I think it's something to do with the .ncb (non compiled browser) file. This file gets generated everytime you open a workspace (if it doesn't exist). Maybe breaking up large files into smaller files may help. HTH Jignesh Patel
-
This has happened to me as well. I still haven't found a solution but I think it's something to do with the .ncb (non compiled browser) file. This file gets generated everytime you open a workspace (if it doesn't exist). Maybe breaking up large files into smaller files may help. HTH Jignesh Patel
That could be, my .ncb file is 10 MB. Unfortunately, my development environment shouldn't force me to break up the files. I wonder....maybe CodeWarrior for Windows can compile MFC? -- Bryan
-
That could be, my .ncb file is 10 MB. Unfortunately, my development environment shouldn't force me to break up the files. I wonder....maybe CodeWarrior for Windows can compile MFC? -- Bryan
10 MB!!?? :eek: Hmmm... mind you, this does tend to get large... You might try renaming it and firing up the project again - I don't think its a file size issue. BTW - (I can't reproduce the problem right now) - have you tried going into Tools | Options and unchecking the code completion stuff on the Editor page? Wonder if there's a connection... later Oops - just noticed you covered this in your original post...
-
10 MB!!?? :eek: Hmmm... mind you, this does tend to get large... You might try renaming it and firing up the project again - I don't think its a file size issue. BTW - (I can't reproduce the problem right now) - have you tried going into Tools | Options and unchecking the code completion stuff on the Editor page? Wonder if there's a connection... later Oops - just noticed you covered this in your original post...
-
10 MB!!?? :eek: Hmmm... mind you, this does tend to get large... You might try renaming it and firing up the project again - I don't think its a file size issue. BTW - (I can't reproduce the problem right now) - have you tried going into Tools | Options and unchecking the code completion stuff on the Editor page? Wonder if there's a connection... later Oops - just noticed you covered this in your original post...
Whenever I delete the .NCB file it gets recreated (with the same size) as soon as I openthe workspace. As for code completion, all those options are off, though we have tried every combination we can think of :) Bryan -- Bryan
-
Whenever I delete the .NCB file it gets recreated (with the same size) as soon as I openthe workspace. As for code completion, all those options are off, though we have tried every combination we can think of :) Bryan -- Bryan
Interested to know whether Jignesh's discovery is the key. Just a thought - would cleaning out the Temp dir have an impact?
-
Interested to know whether Jignesh's discovery is the key. Just a thought - would cleaning out the Temp dir have an impact?
Yes, this worked!!! All I had to do was close the WizardBar, quit and restart Visual Studio and the slowness is gone! Yay! And if you are WizardBar dependent, I've found an *EXCELLENT* replacement that works a lot better than the WizardBar (and doesn't slow me down to boot :-D It's an Add In called Visual Assist: http://www.wholetomato.com/ -- Bryan
-
Yes, the key was this KB Q202591 "BUG: Developer Studio Source and Dialog Editors Respond Slowly" "When editing source code or a dialog resource with the Visual C++ version 6.0 source or resource editors, the user may experience a slowdown in performance. The resource editor shows a noticeable delay when tabbing between controls. In the source editor, the cursor seems to hesitate when passing through function definitions when using the arrow keys. In both instances the CPU usage is near or at 100%. " The resolutions section is wrong in this article. The real resolution is given at the end: close the wizardbar and restart visual studio. Thanks Jignesh. I didn't find this because my keyword search was "off" just a bit... -- Bryan