ManageIQ / ManageIQ/kubeclient
v5 first request is ~10x slower than v4
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 426
- Forks
- 171
- PR merge metrics
- No merged PRs in 30d
Description
Problem: the first request of a new client is somehow 10x slower on v5 (100ms vs 10ms)
Background: I was trying to upgrade our app to v5 (master) to get gzip to resolve https://github.com/ManageIQ/kubeclient/issues/622
c = build_kubeclient(@url, 'api/v1')
Benchmark.realtime { c.get_entity("namespaces", "kube-system") }
master: 0.017
v5: 0.10
since I'm using get_entity I don't think the issue is extra requests, but something is going on ...
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the supplied Benchmark.realtime comparison for build_kubeclient(...).get_entity(...) on v4, v5, and master, then trace the first-request path to locate the source of the latency difference. Done means the v5 first request no longer shows the reported ~10x slowdown; the issue names no files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- api
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100