You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@netbeans.apache.org by John McDonnell <mc...@gmail.com> on 2017/11/13 18:32:29 UTC
How to analyse the debugger performance
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
Re: How to analyse the debugger performance
Posted by Lars Bruun-Hansen <lb...@gmail.com>.
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 <md...@gmail.com>
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
>>
>
>
Re: How to analyse the debugger performance
Posted by Peter Cheung <mc...@hotmail.com>.
in java world, the debugger performance really cant compare with visual studio, when pressing f10 to single step, it response really fast.
should we rebuild the netbeans debugger?
Martin Dindoffer <md...@gmail.com>> 於 2017年11月14日 上午4:39 寫道：
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
Re: How to analyse the debugger performance
Posted by Martin Dindoffer <md...@gmail.com>.
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
AW: How to analyse the debugger performance
Posted by Christian Lenz <ch...@gmx.net>.
In no other application like IntelliJ or Visual Studio, you need to change the size at all. It is still working fast.
Of Course it could be about the using modules, the used Memory, the opened Projects etc.
I realized it too, that the debugger is quite slow sometimes in some cases like jumping to code, maybe it is not about the debugger maybe it is the function where you can go to code when you jump into the code via breakpoints. I think the debugger needs a deeper look to optimize it. I really think, that there can be a lot of improvements.
Cheers
Chris
Von: Lars Bruun-Hansen
Gesendet: Dienstag, 14. November 2017 10:36
An: dev@netbeans.incubator.apache.org
Betreff: Re: How to analyse the debugger performance
2GB sounds too little. What is the reason for being so stingy?
Why not say 8GB?
Jaroslav's suggestion will tell you if you have shortage of heap.
On Tue, Nov 14, 2017 at 9:54 AM, John McDonnell <mc...@gmail.com>
wrote:
> Hi,
>
> @Martin
> I'm not noticing too slow of a Debugger startup time... around 10
> secs (rough counting in my head just there) Its more related to
> breakpoints and moving through them/setting them while debugging
> etc... The Variables windows and evaluating expressions.
>
> @Lars
> I have a 16GB machine and I have given NB 2GB in my netbeans.conf
> file: "-J-Xmx2G" I could attempt to give it another GB more
> possibly...
>
> @Jaroslav
> I'll give that a shot shortly and see if I can spot anything.
>
> Thanks all!
>
> Regards
>
> John
>
>
>
> On 14 November 2017 at 05:42, Jaroslav Tulach <ja...@gmail.com>
> wrote:
> > Hello John,
> > try self profiler:
> > http://wiki.netbeans.org/FaqProfileMeNow
> >
> > From that you should be able to find out what the JPDA threads are doing
> when
> > things are taking too long.
> > -jt
> >
> >>> John McDonnell <mc...@gmail.com>: 13.11.17 @ 18:32 <<
> >> 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
> >
> >
>
Re: How to analyse the debugger performance
Posted by Lars Bruun-Hansen <lb...@gmail.com>.
2GB sounds too little. What is the reason for being so stingy?
Why not say 8GB?
Jaroslav's suggestion will tell you if you have shortage of heap.
On Tue, Nov 14, 2017 at 9:54 AM, John McDonnell <mc...@gmail.com>
wrote:
> Hi,
>
> @Martin
> I'm not noticing too slow of a Debugger startup time... around 10
> secs (rough counting in my head just there) Its more related to
> breakpoints and moving through them/setting them while debugging
> etc... The Variables windows and evaluating expressions.
>
> @Lars
> I have a 16GB machine and I have given NB 2GB in my netbeans.conf
> file: "-J-Xmx2G" I could attempt to give it another GB more
> possibly...
>
> @Jaroslav
> I'll give that a shot shortly and see if I can spot anything.
>
> Thanks all!
>
> Regards
>
> John
>
>
>
> On 14 November 2017 at 05:42, Jaroslav Tulach <ja...@gmail.com>
> wrote:
> > Hello John,
> > try self profiler:
> > http://wiki.netbeans.org/FaqProfileMeNow
> >
> > From that you should be able to find out what the JPDA threads are doing
> when
> > things are taking too long.
> > -jt
> >
> >>> John McDonnell <mc...@gmail.com>: 13.11.17 @ 18:32 <<
> >> 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
> >
> >
>
Re: How to analyse the debugger performance
Posted by John McDonnell <mc...@gmail.com>.
Hi,
@Martin
I'm not noticing too slow of a Debugger startup time... around 10
secs (rough counting in my head just there) Its more related to
breakpoints and moving through them/setting them while debugging
etc... The Variables windows and evaluating expressions.
@Lars
I have a 16GB machine and I have given NB 2GB in my netbeans.conf
file: "-J-Xmx2G" I could attempt to give it another GB more
possibly...
@Jaroslav
I'll give that a shot shortly and see if I can spot anything.
Thanks all!
Regards
John
On 14 November 2017 at 05:42, Jaroslav Tulach <ja...@gmail.com> wrote:
> Hello John,
> try self profiler:
> http://wiki.netbeans.org/FaqProfileMeNow
>
> From that you should be able to find out what the JPDA threads are doing when
> things are taking too long.
> -jt
>
>>> John McDonnell <mc...@gmail.com>: 13.11.17 @ 18:32 <<
>> 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
>
>
Re: How to analyse the debugger performance
Posted by Jaroslav Tulach <ja...@gmail.com>.
Hello John,
try self profiler:
http://wiki.netbeans.org/FaqProfileMeNow
From that you should be able to find out what the JPDA threads are doing when
things are taking too long.
-jt
>> John McDonnell <mc...@gmail.com>: 13.11.17 @ 18:32 <<
> 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