Hi,
I'm sorry that the mentioned PR caused some errors for files without a
corresponding parser (thanks for fixing it), but I'm wondering why this
particular PR should harm the indexing performance so much?
To solve the problem, is it possible to start NB with a fresh userdir,
invoke the
kef>
From: Michael Bien
Sent: Wednesday, May 25, 2022 6:41:57 PM
To: dev@netbeans.apache.org ; John Neffenger
Subject: Re: Very poor code indexing performances
On 26.05.22 01:18, John Neffenger wrote:
> On 5/25/22 10:27 AM, Michael Bien wrote:
>> async-profiler[1] combined wi
On 26.05.22 01:18, John Neffenger wrote:
On 5/25/22 10:27 AM, Michael Bien wrote:
async-profiler[1] combined with flame graphs can be helpful to find
bottlenecks of long running tasks (> few seconds).
+1 for async-profiler! It can let you get a much bigger picture than
is possible with most
On 5/25/22 10:27 AM, Michael Bien wrote:
async-profiler[1] combined with flame graphs can be helpful to find
bottlenecks of long running tasks (> few seconds).
+1 for async-profiler! It can let you get a much bigger picture than is
possible with most other profilers, and it often shows you
Hi,
this might be related:
https://github.com/apache/netbeans/pull/3516
I also had the feeling, that performance suffered from it, but Dusan
neither reacted to a direct fix for things, that were broken by that
PR, nor to later requests for other performance fixes.
Might be worth trying to
Hello,
Since NB 13 and Java 17, I am experiencing again poor code indexing
performances as it used to be with older version of NB. 12.4 was running
fine.
I checked the IDE logs and see only entries like:
INFO [null]: Last record repeated again.
WARNING
