Re: Very poor code indexing performances

Since talking performance…Just curious…is it conceivable to add some performance test for use during build time testing and gather metrics during a given build so with each build/release to get performance historical over time? Get Outlook for iOS

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 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

Re: Very poor code indexing performances

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

Re: [RELEASES] 14 remaining issues

Hi, Am Mittwoch, dem 25.05.2022 um 21:54 +0200 schrieb Eric Barboni: > I see the thread of Jean-Marc on the indexing perf. Matthias do you want to > try to revert on NB14 or on NB 15 ? no. This won't be quick and surely nothing to be rushed in. Greetings Matthias

Re: [RELEASES] 14 remaining issues

I'd vote for NB15 and more analysis on that one. This NB14 starts to feel like a never ending story. On 5/25/22 12:54, Eric Barboni wrote: Hil, Release build is back. I may change it after this release to use more standard github orga instead of ASF special plugin (waiting for infra on this

RE: [RELEASES] 14 remaining issues

Hil, Release build is back. I may change it after this release to use more standard github orga instead of ASF special plugin (waiting for infra on this point) We have 2 PR merged for rc6 (rc5 is lost in space bug fixe + performance). I see the thread of Jean-Marc on the indexing perf.

Re: Very poor code indexing performances

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

Very poor code indexing performances

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

RE: [RELEASES] 14 remaining issues

Hi Neil, Congrats for your new home I had no follow up to the ticket yet. I tried to rerun yesterday with the same timeout issue (I have no clue others similar job are ok maybe our gitbox is too huge). As I used rc5 we could go for rc6. We could merge PR meanwhile. Regards Eric -Message

Re: [RELEASES] 14 remaining issues

On Tue, 24 May 2022 at 11:36, Michael Bien wrote: > if this PR would cause another RC and another week delay i think we > should leave it out. Well, we haven't been able to build RC5 yet as far as I know?! So, shouldn't delay further and might be good to have. I might also add