Repository navigation
docs: re-measure latency with Safe Browsing enabled - #1
Merged
Merged
Conversation
Safe Browsing is now configured in production. New URLs are no slower within run-to-run noise (450 ms and 706 ms medians). The model blocked one more legitimate URL in this run, now 2 of 50 overall.
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
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.
Safe Browsing (
SAFE_BROWSING_API_KEY) is now set in production, so I re-ran the latency suite against the deployed Worker. Google's phishing and malware test pages now come back blocked as "Listed by Google Safe Browsing".Re-measured 2026-10-08 from Belgium (Cloudflare CDG). Median time to first byte, network included:
401)No measurable cost from Safe Browsing. It runs in parallel with the cache read and RDAP, and the differences are within run-to-run noise.
Model false positives: in this run the model blocked
citi.com/aps-timing2, reading my made-up test path as a "suspicious subdomain". Withnya5.comfrom the first run, that makes 2 of 50 new URLs on legitimate domains. The README now says so.README only, no code changes. The site's claims in itsF4LCON/xivlabs#4 (about 100 ms cached, about half a second new) still hold.