ComponentTracker is very slow

[Freeman656]

Description of the bug

When using Vaadin > 24 is dev mode, the ComponentTracker is very slow which make the whole application very slow.

This is annoying most of the time for very low reward (knowing where the component has been created/attached is helpful just a few times during development).
This is also very noticable when using JProfiler because the recording streches up all superficial calls (see attachment)

Expected behavior

The most practical way I see it is by adding a property to avoid the tracking, in addition to the productionMode.
This would solve the performance issue if needed by the developer, and would also still allow other to continue the tracking.

Minimal reproducible example

The best way is to create a page with ~100 select containing each ~1000 elements with custom renderer (this is not my case but this would trigger the performance issue)

Versions

• Vaadin / Flow version: 24.2.3
• Java version: 21.0.1

[mcollovati]

I tried locally with 100 selects with 1000 items and component renderer as suggested.
Page rendering is, of course, slow, but for me, the time consumed by ComponenTracker is irrilevent (less than 1 millisecond per each call).
Also disabling the ComponenTracker, I can't see relevant differences in page load

[mcollovati]

Anyway, it should be safe to add a configuration property to disable ComponentTracker in dev mode

[Freeman656]

Thanks for your investigation. As you mentionned it's taking less than an ms for each call but called 100k times, it's starting to feel like 10 to 60 seconds for the page to load, when compared with the production mode which is around 2 to 3s.
I agree on the configuration property, it's safe to do and doesn't require heavy modifications...

[vaadin-bot]

This ticket/PR has been released with Vaadin 24.4.0.alpha1 and is also targeting the upcoming stable 24.4.0 version.