Probe a real outbound fetch alongside the local probes - #1673
Merged
Conversation
Cache and timer probes come back in single-digit ms while the same requests take 4-6s wall, so local I/O is not the cost. Neither probe leaves the isolate. Time a real outbound subrequest, the class the docs proxy implicates (0.098s direct vs 3-6s through the Worker).
Contributor
Cloudflare previewTorn down — the PR is closed. |
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.
The previous probes came back:
preWorkMs0-4ms,cacheProbeMs2-21ms,timerProbeMs1ms — on requests whose wall time was 4000-7800ms.So there is no startup/queue penalty, and local I/O (Cache API, timers) is fast. Both of those probes stay inside the isolate. The one class not yet measured is a real outbound network subrequest, which is exactly what the docs proxy implicates:
executor.mintlify.devanswers in 0.098s directly and 3-6s through the Worker.This times a fetch to a small unrelated endpoint on every request. If
fetchProbeMsis seconds, outbound subrequests are the cost and the search narrows to why.