Comments on: Tip: Netbeans 6.x scanning performance fix

By: Rob Haag

Rob Haag — Thu, 12 Jan 2012 10:43:07 +0000

Thank You! Just got a Win. machine (linux nerd myself)…same issue for me…even now using NB 7.1 on Windows 7 (64bit). Have a 2 core (intel 6200) w/ 4gb of RAM…your fix made a huge difference. I’m remoting to my Linux box so I can take the show on the road now and again, but even with a local project (empty) the ‘scanning’ was hanging forever on 100% mark.

By: Thorsten

Thorsten — Mon, 28 Feb 2011 09:05:35 +0000

Thanks for this article. The CPU usage of netbeans was realy horrible.

Noe after changing the config it is realy usable. Maybe I will try the scan ondemand plugin later.

thanks

By: g

Sun, 29 Aug 2010 06:27:35 +0000

that’s right!

combination of enabling Scan On Demand Plugin
and also disabling Mercury Plugin

make our CPU Usage more safer… and lower of course…
glad to hear everything is now stable…

By: Bruce

Bruce — Wed, 19 May 2010 14:55:32 +0000

I also noticed there’s a “Scan on Demand” plugin available for 6.8RC2, allowing you to disable automatic scanning and run it when you want it to run.

By: Roy

Roy — Sat, 17 Apr 2010 17:45:25 +0000

But if you use Scan on demand, you indexes could be out of date and could cause some lost of data.

By: hemuman

hemuman — Mon, 15 Feb 2010 20:48:27 +0000

My problem Solved with “Scan on Demand”. It use to scan for ages….
thanks Adam Overlock

By: Tres Finocchiaro

Tres Finocchiaro — Mon, 25 Jan 2010 18:32:21 +0000

I’m experiencing this on Windows 7 Enterprise x86 single core CPU. I will try the suggested work-around, however I agree with the Netbeans developer that fixing this as part of the release cycle makes it better for stuff like upgrading.

The release information:
Product Version: NetBeans IDE 6.8 (Build 200912041610)
Java: 1.5.0_22; Java HotSpot(TM) Client VM 1.5.0_22-b03
System: Windows 7 version 6.1 running on x86; Cp1252; en_US (nb)
Userdir: C:\Users\tfino\.netbeans\6.8

-Tres

By: Mike

Mike — Tue, 22 Dec 2009 16:23:53 +0000

I have the same issue with 6.8. The CPU usage is not always high, but the UI is so slow it is unusable. I am going to try upping the heap. Thanks for the post.

By: Randy

Randy — Sat, 19 Dec 2009 06:33:54 +0000

If scanning was properly implemented in Netbeans, it would be in a discrete thread, prioritized lower than the app. It’s insane that when it scans, you can’t do anything else. Yes, in 6.8 this happens.

I have a quad core, and the app is locked scanning with less than 5% cpu usage.

By: Adam Overlock

Adam Overlock — Thu, 10 Dec 2009 21:31:02 +0000

I also noticed there’s a “Scan on Demand” plugin available for 6.8RC2, allowing you to disable automatic scanning and run it when you want it to run.