-
Notifications
You must be signed in to change notification settings - Fork 166
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
getting large resources on slow connection is slow #622
Comments
grosser
changed the title
getting many resources is super slow and super memory-leaky
getting large resources is slow and memory-leaky
Nov 18, 2023
grosser
changed the title
getting large resources is slow and memory-leaky
getting large resources on slow connection is slow
Nov 18, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Version
version 4.11.0 + master (054bff2)
Problem
getting many resources is slow compared to
kubeclient --raw
, especially when going cross-region, cluster-local is much better (local: 6s vs 2s remote: 50s vs 12s)Solution
enable gzip or recommend in the readme to enable gzip
... no idea for memory
Background
comparing
with
ps -o rss= -p 74108
andGC.start
alternative:
GC.start; sleep 10; (Integer(File.read("/proc/#{Process.pid}/statm").split(" ")[1]) * 4096.0 / 1024 / 1024).round
kubectl in ruby takes ~12s and 50mb of memory
kubeclient takes 40s and 600mb initial + ~300 inc of memory (leaking but eventually gets gced, unclear why it takes so long)
with
using without
parsed_symbolized
is 5s slower and uses even more (1GB)FYI
as: :raw
did not help either--http2
same result--compressed
makes that ~17sThe text was updated successfully, but these errors were encountered: