2026 update - #7
Open
ChloeQuijano wants to merge 1 commit into
Open
Conversation
Connected via a bare wss://connect.anchorbrowser.io?apiKey=... URL, which isn't how Anchor Browser's API works today. Anchor Browser's blog-published connection numbers (5,582ms avg, ~8x every other provider) were very likely measuring this broken/outdated path rather than Anchor's real performance. Fixed to match Anchor Browser's current API: POST /v1/sessions to create a session, use the returned cdp_url to connect, DELETE /v1/sessions/:id to tear down. Verified with a live run against all 4 providers -- Anchor Browser's connection time now lands in the same range as the other three (243-689ms depending on run/region), not an 8x outlier.
ChloeQuijano
changed the title
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
providers/anchorbrowser.jswas connecting via a barewss://connect.anchorbrowser.io?apiKey=...URL — not how Anchor Browser's API works today. This is very likely why the published blog benchmark showed Anchor Browser's connection time as an extreme outlier (5,582ms avg, ~8x every other provider): that number was probably measuring a broken/outdated connection path, not Anchor's real performance.Fixed to match Anchor Browser's current API:
POST /v1/sessions(headeranchor-api-key) to create a sessiondata.cdp_urlDELETE /v1/sessions/:idto tear downVerification
Ran all 4 providers live,
TOTAL=10againstexample.com(this tool's existing default config, unchanged), (Ubuntu 22.04.5 LTS, x86_64, 1 vCPU, ~454MB RAM, Node v22.23.2, npm 10.9.8).Numbers below pool all 3 runs (30 iterations/provider): Average is the mean of the 3 runs' averages, Fastest/Slowest are the min/max across all 3 runs — more stable than any single run.
Connection Speed (ms)
Page Creation Speed (ms)
Navigation Speed (ms)
Anchor Browser's connection time now lands in the same range as the other three providers — no longer an 8x outlier.