viewing over 50 endpoints in k9s, the CPU usage reaches 100%

[eternam2]

Below is a draft for the issue to be submitted to the k9s GitHub repository based on the template you've shown, and including the details you've provided about the CPU usage issue when viewing over 50 endpoints:

Describe the bug
When viewing over 50 endpoints in k9s, the CPU usage reaches 100%, making it difficult to interact with the application properly. This occurs consistently when the endpoints view is populated with more than 50 entries, indicating a potential performance optimization issue in views handling large sets of endpoints.

To Reproduce
Steps to reproduce the behavior:

Launch k9s.
Navigate to the endpoints view by typing :ep.
Observe the CPU usage as the endpoints populate the view, especially when the total number exceeds 50.
Historical Documents

No additional documents available. Issue reproducible on current setup without specific configurations or resource manifests.
Expected behavior
I expected the application to handle large numbers of endpoints without significant degradation in performance. The CPU should not spike to 100%, and the application should remain responsive, allowing for continuous monitoring without performance penalties.

Screenshots
If applicable, screenshots of the CPU usage spike could be added here to illustrate the issue.

Versions (please complete the following information):

OS: CentOS 7
K9s: 0.32.4
K8s: 1.26.14