https://issues.apache.org/jira/browse/NETBEANS-2409?focusedCommentId=16822009&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16822009
On 4/12/19 12:54 PM, Scott Palmer wrote:
Another strange thing. If I type:
someIdentifier.
I get an automatic auto-complete popup after typing the ‘.’, populated with all the
methods or members I could finish with. But as soon as I type one letter, eg .’i’ (to
select "isSomething()"), then I get a “Please wait…” and a few seconds of
delay! The entire list of possibilities was already presented to me, narrowing it down
after I hit another letter should be instant. Something is going wrong.
Attached Snapshot data…
Scott
On Apr 12, 2019, at 3:34 PM, Kodewerk <[email protected]> wrote:
Hi Scott,
Please export Snapshot data. As I mentioned before, this is likely a stalled
thread and as such an execution profiler is likely to not report it. The most
useful view IME are thread dumps at about 1 second intervals.
Kind regards,
Kirk
On Apr 12, 2019, at 12:23 PM, Scott Palmer <[email protected]> wrote:
I just experienced a 10s delay before the auto-complete popup appeared (did see
the “Please wait…” though). That was the second press of auto-complete at the
same spot. The first attempt took 8 seconds. I triggered the profiling for
each, but I suspect the first attempt may be tainted because the Gradle project
was stuck loading - there was a dependency that it couldn’t get. I commented
out that dependency (didn’t need it) so project was loaded fully and tried
again. This is with a very tiny toy project. I single-class microbenchmark
using the JMH gradle plugin.
There are options to export “Sanpshot Data”, “Forward Calls”, “Hotspots” …
which of these do you want?
Scott
On Apr 12, 2019, at 12:06 PM, Jan Lahoda <[email protected]> wrote:
Hi Scott,
In this case, it might be useful/helpful if we had the self profiler snapshots.
Possibly for one of the features, e.g. code completion:
http://wiki.netbeans.org/FaqProfileMeNow
<http://wiki.netbeans.org/FaqProfileMeNow>
(Refactoring/findusages is currently much faster with nb-javac than without it,
but the difference should be much smaller for code completion, etc.)
Jan
12. dubna 2019 16:26:29 SELČ, Scott Palmer <[email protected]> napsal:
What is the best course of action for reporting slowness? I can’t share my
project.
I’m not certain how to give step-by-step instructions when the problem is
basically one step in most cases. E.g. invoke auto-complete - nothing happens for
several seconds. Invoke rename - dialog doesn’t appear for several seconds. Find
usages - extremely slow > 5 second delay on a private member of a class less
than 100 lines.
In general it seems NB 11 is noticeably slower than NB 8.2. Not good
considering slowness was already my #1 complaint about NB 8.2. I have so far
found the benefits of NB outweigh the fact that it is much slower than other
IDEs for the same operations, but the slowness of NB 11 is tipping the scale.
I don’t want to switch IDEs, pease don’t interpret this as some sort of threat
to do so. I would like to help find the issues in NB. But I don’t have the
bandwidth to debug NB and not being about to share my project makes it
difficult to provide helpful reports :-(
Are others seeing the slowness?
Find usages, renames, call-hierarchy, auto-complete… things I use all the time,
I often have to wait 5 to 10 seconds for a response from the IDE, sometimes
more.
I’ve already deleted user dir and cache and restarted.
I’m using Gradle-based Java projects, running NB 11.0 with JDK 8u202.
Is there a wiki page with instructions on profiling the IDE? Maybe I can
collect something useful.
Scott
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists