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.

Sign up for GitHub

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

Jump to bottom

Optimize collection of events with sorted timestamp #135

Open
black-dragon74 opened this issue Mar 13, 2024 · 5 comments
Open

Optimize collection of events with sorted timestamp #135

black-dragon74 opened this issue Mar 13, 2024 · 5 comments
Assignees
@black-dragon74

Comments

@black-dragon74
Copy link
Collaborator

While testing I noticed, In case of a large number of events, hitting the API server from inside a loop may lead to mg getting stuck. Optimize this process.
@black-dragon74 black-dragon74 self-assigned this Mar 13, 2024
@black-dragon74
Copy link
Collaborator Author

black-dragon74 commented Mar 13, 2024 •
edited
Loading

Maybe add a MAX celiling to number of events to collect? As the list might get too large too soon on busy clusters.

@black-dragon74
Copy link
Collaborator Author

Thoughts @yati1998 ?

@yati1998
Copy link
Member

I am not sure about it, there was a request from QE to collect them, let me find the bug and mention it here. I think they would need all of the events.

@black-dragon74
Copy link
Collaborator Author

@yati1998, did you mean this: https://bugzilla.redhat.com/show_bug.cgi?id=2180471 ?

@yati1998
Copy link
Member

@yati1998, did you mean this: https://bugzilla.redhat.com/show_bug.cgi?id=2180471 ?

yes

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@black-dragon74 black-dragon74

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@black-dragon74 @yati1998