Conversation
pod_api_request resolved the pod-api-requester (list pods, read node, read service) with the blocking k8s client on every publish. That stalls the event loop, so the publish period became max(delay_after_publish, lookup time). Over the Rancher proxy the lookup took 2.08 s on 2026-08-15, and the whole v2.3.0 matrix published at 0.48 msg/s instead of 1. The run now resolves the address once before the publish loop and passes it down; pod_api_request keeps the lookup for callers that do not pass one. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Resolves the pod-api-requester address once before the publish loop. The per-message lookup blocked the event loop, so a slow k8s API stretched the publish period (the v2.3.0 matrix ran at 0.48 msg/s instead of 1).