In my experience working with many open projects is not per se something which is slowing NetBeans down. However, working with many open projects *and* not enough memory is. If NetBeans doesn't have enough memory to work with then things will become slow.
Do you have enough RAM on your machine and - just as important - are you letting NetBeans have enough of it? If I remember correctly, on JDK8 the default max heap setting is 1/4 of the physical RAM. So if your workstation has 16 GB then NetBeans will by default not be allowed to use more than 4 GB of those. Give it some more! Fix memory allocation in etc/netbeans.conf if needed. At least this is worth looking into before you start more time consuming adventures. :-) On Mon, Nov 13, 2017 at 9:38 PM, Martin Dindoffer <[email protected]> wrote: > Hi John, > > Do you also observe very long durations of debugging session > initialization? > I'm asking, because that's what I'm dealing with every day when I try to > attach the debugger to a process. > JPDA seems to connect and then it stays stuck for a few seconds until the > thread lists gets populated. > And yes, it seems that a big number of opened projects / maven modules is > a common denominator. > > Martin > > > Hi, >> >> At work, I have in my project group with just over 100 open projects. >> Whenever I attempt to debug the application, I find the >> debugger/NetBeans slow and sluggish. >> >> Now I'm not sure if this is related to the number of open projects, >> the number of breakpoints I have, or indeed the webapp I'm debugging, >> but unfortunately, I sit next to an IntelliJ user and they don't seem >> to have the same issues, with an identical machine. So I must assume >> its NetBeans related.... >> >> I want to start to analyse why this is happening, maybe get enough >> content to raise/fix? a defect etc. >> >> What would be the first set of steps? >> >> Regards >> >> John >> > >
