docs(plans): non-AWS bare metal cost+feasibility for worker pps scaling (research)#78
Draft
skullcrushercmd wants to merge 1 commit intomainfrom
Draft
docs(plans): non-AWS bare metal cost+feasibility for worker pps scaling (research)#78skullcrushercmd wants to merge 1 commit intomainfrom
skullcrushercmd wants to merge 1 commit intomainfrom
Conversation
…ps scaling ENA on kernel ≤6.19.11 has no driver-mode AF_XDP zerocopy, capping c6in.metal at ~22M pps. Survey enumerates Equinix Metal, Hetzner, OVH, Latitude.sh, Vultr BM, and Servers.com on hardware (Mellanox/mlx5 ConnectX), pricing, mlx5 zerocopy support in mainline (verified against drivers/net/ethernet/mellanox/mlx5/core/en/xsk/setup.c), egress, and AUP for scanning. Headline finding: AUP risk dominates $/Mpps. Hetzner and OVH explicitly prohibit port scanning; Equinix Metal is sunsetting 2026-06-30; Latitude.sh is the credible primary candidate (Fair Usage Policy is DDoS-focused with no explicit port-scan ban) with Servers.com EBM as backup. Doc proposes a $2k-ceiling experiment on Latitude.sh rs4.metal.large (2× 100G, $1,471/mo) gated on written AUP and NIC-vendor confirmation. Co-Authored-By: Claude Opus 4.7 (1M context) <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
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
Research-only planning doc — no engine code, no script changes. Scopes the cost and feasibility of moving AnyScan port-scanner workers off AWS to non-AWS bare metal with Mellanox/mlx5 ConnectX NICs, motivated by the ENA-on-kernel-≤6.19.11 driver-mode AF_XDP zerocopy gap that caps
c6in.metalat ~22M pps.The doc covers Equinix Metal, Hetzner, OVH, Latitude.sh, Vultr BM, and Servers.com:
drivers/net/ethernet/mellanox/mlx5/core/en/xsk/setup.c)Headline findings
rs4.metal.large(2× 100G, $1,471/mo) is the recommended experiment box.Recommended path
A single-instance, two-week, $2k-ceiling experiment on Latitude.sh
rs4.metal.large, gated on (1) written AUP confirmation, (2) NIC-vendor confirmation (Mellanox vs Broadcom), (3) egress overage rate. Hypothesis: ≥45M pps (≥2× ENA-AF_XDP), $/Mpps in the $15–18/mo range vs ~$249 onc6in.metal.Test plan
rs4.metal.largeis Mellanox at 100G (the doc flags this as "confirm before commit")🤖 Generated with Claude Code