You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The 'kamel' binary is spending a lot of time in initialization. I suspect it's initializing caches and metadata for all object kinds present on the remote cluster.
A simple command like 'kamel run it.groovy' can take up to 10/15 seconds but it literally needs to do a simple POST with Json data.
There are command line tools (e.g. stern) that are much faster on the same cluster (1/2 seconds to do their job).
I think we should review our usage of the double kind of client in our project and disable unneeded features when running in CLI mode.
The text was updated successfully, but these errors were encountered:
The 'kamel' binary is spending a lot of time in initialization. I suspect it's initializing caches and metadata for all object kinds present on the remote cluster.
A simple command like 'kamel run it.groovy' can take up to 10/15 seconds but it literally needs to do a simple POST with Json data.
There are command line tools (e.g. stern) that are much faster on the same cluster (1/2 seconds to do their job).
I think we should review our usage of the double kind of client in our project and disable unneeded features when running in CLI mode.
The text was updated successfully, but these errors were encountered: