Re: Is there any way to stop the scanning projects?

yes - my typo - when i open all the netbeans sources there are many projects.
I used to use ScanOnDemand - when i check the link now,http://deadlock.netbeans.org/hudson/job/nbms-and-javadoc/lastStableBuild/artifact/nbbuild/nbms/updates.xml.gz

and reference in nb8.1 - ScanOnDemand is not present.
Googling i found Bug 248993 – SCANONDEMAND PLUGIN BREAKS IDE 8.0.2 ***CONFIRMED***
|   |
|   |   |   |   |   |
| Bug 248993 – SCANONDEMAND PLUGIN BREAKS IDE 8.0.2 ***CONFIRMED***[?]  | New | Browse | Search | Reports | Help | Log In First Last Prev Next    This bug is not in your last search results.  |
|  |
| View on netbeans.org | Preview by Yahoo |
|  |
|   |


seems ScanOnDemand is no longer available.
-Gary 

    On Friday, December 18, 2015 9:57 AM, geertjan wielenga <[email protected]> wrote:
 

 
On 18-12-2015 17:49, emiddio-frontier wrote:
> This suggestion does not completely work - it helps some; i always have that
> checkbox checked (for years and multiple versions of netbeans) and i still
> gets tons of scanning; there are win32 filewatcher threads running in
> netbeans and they get notified when files change. also applies to
> favorites,not just folder in projects.
>
> i sometimes wonder if you folks at netbeans dev really use netbeans like the
> real world. if you open all of netbeans's sources at same time - all the nb
> projects of netbeans you have large project.

No, instead, then you have hundreds of projects. NetBeans IDE is 
modular. It is not one single project.


>
> but i routinely have 50+ projects open - could be jax-ws, glassfish sources,
> 20+ related projects where i work and others.

NetBeans devs typically work with hundreds of projects.

Have you read this document, it could help you: 
http://wiki.netbeans.org/ScanOnDemand

Gj


>
> i have a 16GByte ram 64bit fast laptop provided from work - 16 cpu cores -
> and netbeans 8.1 consumes huge amounts of cpu - and takes long time to
> refactor. when i profile netbeans to try to see what is going on it is
> mostly in some win32 native method usually doing some kind of file watching,
> and waiting for a condition to proceed.
>
> regarding snapshots and reports i have submitted where netbeans pops up
> dialog saying ... took 45 seconds - do you want to report it.. or similiar -
> i get 'wont fix' and issue closed- related to windows filesystem.
>
> seems to me either bug/bad design in windows or jdk or some subtle bad
> design in netbeans - i have not been able to figure it out myself - i have
> tried some - a few hours - debugging netbeans and referencing the netbeans
> sources.
>
> i run netbeans on solaris remotely - so it is slow due to remote xwindows
> and only use locally on windows 7 pro laptops. I have installed in windows
> 10 but dont use that laptop much.
>
>
> -Gary
>
> ----- Original Message -----
> From: "geertjan wielenga" <[email protected]>
> To: <[email protected]>
> Sent: Thursday, December 17, 2015 10:08 PM
> Subject: [nbdev] Re: Is there any way to stop the scanning projects?
>
>
> See screenshot.
>
> Gj
>
> On 17-12-2015 22:00, rkris1 wrote:
>> an individual scan doesn't necessarily take a long time, but background
>> scanning occurs almost constantly, stopping and starting over and over and
>> over, with the "background scanning..." message popping up into the status
>> bar over and over many times per minute. this just started happening
>> recently and i have no idea why. it isn't impacting usability as far as i
>> can tell, but it does mean that netbeans is constantly consuming a fair
>> amount of CPU even when not in active use.  and moreover, it's incredibly
>> distracting when trying to code to have your attention pulled to the
>> status bar over and over.  i was trying to learn some new languages using
>> netbeans, and i'm switching over to a different IDE solely because of it,
>> which is a shame, because it's otherwise a great IDE.  but it's super
>> weird that variations on this theme seem to have been around for many
>> years with no real solution or answers to what might be causing it.
>>
>>
>>
>>
>