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
When having many API keys, the Data --> Ingestion view becomes unresponsive.
Steps to reproduce the behavior:
Create 700 API keys
Go to Data --> Ingestion in Firefox
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:
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.
The text was updated successfully, but these errors were encountered:
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.
When having many API keys, the Data --> Ingestion view becomes unresponsive.
Steps to reproduce the behavior:
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:
Environment (please complete the following information):
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.
The text was updated successfully, but these errors were encountered: