Optimize swap quoting debounce timings#89
Merged
techgangboss merged 1 commit intomainfrom Mar 30, 2026
Merged
Conversation
Reduce artificial delays in the input → validated quote pipeline. The 1.5s barter debounce was unnecessary since it fires after the quote RPC already absorbed typing latency. The 1.5s minimum display timer forced users to wait even when results were ready instantly. - Barter validation debounce: 1500ms → 300ms - Min "Calculating..." display: 1500ms → 500ms - Quote fetch debounce: 500ms → 300ms Expected improvement: ~2s faster quote display after user stops typing. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
Summary
Shaves ~2s off the input → validated quote pipeline. All existing deduplication and staleness guards (requestIdRef, AbortController, inputKey dedup) handle the tighter timings correctly.
Context: Owen's #claws investigation confirmed the 1.5s is a frontend input debounce artifact, not execution latency. Three debounces were stacking to add ~2.5s of artificial wait before the user sees a validated quote.
Test plan
🤖 Generated with Claude Code