-
Notifications
You must be signed in to change notification settings - Fork 8.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Ingest Manager] perceived performance drop in /api/ingest_manager/epm/packages api response which is what loads Integrations to be added to a configuration #71289
Comments
In 7.9, we added support for limiting integrations on an agent config (#70542). Part of this includes removing limited integrations which already exist on the selected agent config or disabling agent configs which already have that integration (depending on what is part of Step 1). This was accomplished via making an additional call to get the list of limited integrations (first request shown in the above screenshot), which will indeed slow down the initial loading of Step 1. @EricDavisX Do you feel that the performance drop significantly degrades UX enough to warrant effort to improve it? @ph I will remove beta1 label from this for now. |
@jen-huang if it doesn't have any bad side effect we push it to later releases. I am +1 to remove the beta label. |
Pinging @elastic/ingest-management (Team:Ingest Management) |
I do think it warrants review. If any low hanging fruit exist to improve, I'd prioritize as high and try to get it in sooner. Anything harder is debatable. @ph I'd put this on the list for 7.11. Unless you try it out and decide its ok enough. Personal repeat experience makes me want to fix it for 7.10. :) |
@EricDavisX I am going to assign it to myself do a few testing. |
I found a bug which would cause this page to be slow 🤦♀️ Reassigning to myself to fix. |
Kibana version:
8.0 Cloud deploy
Browser OS version:
Chrome on macOS
Describe the bug:
I can't say this is a good performance test, but if we feel the hacky data presented here is enough we can do more formal tests and get instrumentation out (or stop-watches etc). I did a recording with what I had available, I acknowledge I didn’t even check which cloud-providers are in use and the stats of the machines!
... but I feel like with Google and 8.0 and the default cloud configuration over the last few weeks there was a point that it got slower. That's all I can say.
Steps to reproduce:
this is what I did, but is also theoretical, as I acknowledge above I don't have more instances spun up to compare better apples to apples
Expected behavior:
the package load time should be just as quick, or quicker.
Screenshots (if relevant):
integration-adding-list-timing.mov.zip
The text was updated successfully, but these errors were encountered: