[
https://issues.apache.org/jira/browse/CAMEL-25438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-25438.
---------------------------------
Fix Version/s: 4.23.0
Resolution: Fixed
Fixed by https://github.com/apache/camel/pull/27544: tabs that are not shown no
longer load on an integration change, and the tabs that need the classpath
share one jvm answer. Selecting an integration now sends no action.
> camel-jbang - monitor tabs wait seconds behind data loads for tabs that are
> not shown
> -------------------------------------------------------------------------------------
>
> Key: CAMEL-25438
> URL: https://issues.apache.org/jira/browse/CAMEL-25438
> Project: Camel
> Issue Type: Improvement
> Components: camel-jbang
> Reporter: Claus Ibsen
> Priority: Minor
> Fix For: 4.23.0
>
>
> The camel-jbang monitor's tabs that ask the selected app for data (Threads,
> Beans, Startup, Type Converters, Diagram, JFR) stay on "Loading..." for 2-5 s
> after an app is selected, and 8-20 s when switching between apps.
> Measured with 4 apps and 7 infra services running:
> * an action alone takes ~1 s, whatever its size (thread-dump, bean,
> startup-recorder, type-converters): the CLI connector looks for an action
> once per 1 s loop;
> * the monitor sends one action at a time per app;
> * selecting an app sends 4 actions for tabs that are not open: jvm 3 times
> (Classpath, CVE Audit and Maven Dependencies each load the same classpath in
> onIntegrationChanged) and route-structure (Catalog);
> * the tab the user opens waits behind them: Beans asked for at 0.3 s was
> answered at 3.6 s, Startup asked for at 4.7 s at 8.6 s.
> Fix: a tab that is not shown does not load on an app change (it loads when it
> is opened, as onTabSelected already does), and the jvm answer is shared by
> the tabs that need the classpath.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
