Skip to content
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

Data --> Ingestion page very slow with many API keys #1877

Closed
Sebbl22 opened this issue Jun 26, 2023 · 2 comments
Closed

Data --> Ingestion page very slow with many API keys #1877

Sebbl22 opened this issue Jun 26, 2023 · 2 comments
Labels
Milestone

Comments

@Sebbl22
Copy link

Sebbl22 commented Jun 26, 2023

When having many API keys, the Data --> Ingestion view becomes unresponsive.

Steps to reproduce the behavior:

  1. Create 700 API keys
  2. Go to Data --> Ingestion in Firefox
  3. Firefox uses a unusual high amount of CPU and the page becomes unresponsive. Sometimes the page would not even open.

Expected behavior
The page should be responsive with any amount of API keys.

Screenshots
Resizing the page in Firefox has a noticeable delay. Firefox is already resized, but the content is not:
grafik

grafik

Environment (please complete the following information):

  • OS: Windows 10 22H2 64-bit
  • Browser: Firefox 114.0.2 64-bit, Edge 114.0.1823.51 64-bit, Chrome not tested
  • Seq Version: Seq 2023.1.8991
  • Using Docker? No

Additional context
I am guessing, that the issue is related to the large amount of diagrams (1 per API key) on the Data --> Ingestion page, because they load in very slow.

@Sebbl22 Sebbl22 added the bug label Jun 26, 2023
@KodrAus
Copy link
Member

KodrAus commented Jun 26, 2023

Thanks for the report @Sebbl22. This is definitely something we should fix 👍

@nblumhardt nblumhardt added this to the 2023.3 milestone Jul 11, 2023
@nblumhardt
Copy link
Member

The upcoming 2023.3 build improves this significantly, by batching network requests, dropping the resolution of per-API key ingestion sparklines, and not showing sparklines when more than 200 keys are present (filtering the table below 200 entries will cause sparklines to show).

In a future release we might improve on this further by paginating the list.

The new build will be available next week, it'll be good to hear how it goes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants