Compare cost per kept result
Dollars per gigabyte is the wrong number to shop on. What actually matters is the cost of a kept row, a successful check, or a completed account step, and the two pools can swap places the moment you measure it that way. Volume Residential runs $0.89/GB and Premium Residential runs $5.00/GB, so on paper Volume looks like the obvious pick. That sticker gap only holds if both pools keep results at the same rate, which they often do not.
| Pool | Good fit | Bad fit |
|---|---|---|
| Volume residential | Large public pages, broad geo checks, forgiving targets | Expensive targets with heavy blocks. |
| Premium residential | Sensitive targets, lower retry tolerance, stronger ASN needs | Cheap pages where volume already works. |
Work through the arithmetic and the gap narrows fast. If Volume burns four retries to land one useful result while Premium lands it on the first try, the cheaper gigabyte is no longer cheaper per kept row, and the higher sticker price can be the lower real bill.
Bandwidth is where cheap plans get expensive
The hidden cost of a cheap pool is the bandwidth nobody counts. Retry loops, images, blocked HTML pages that still download in full, JavaScript bundles, redirects, and app probes all burn gigabytes, and your application usually credits only the one final useful action. The proxy meter is not so selective: it bills every byte that crossed the wire. The honest number, then, is total GB divided by kept results, and that ratio should decide the pool, not anything printed on a sales page.
Run the same target on both pools
The only way to settle this for your workload is a side-by-side run. Hold the target, country, client, retry limit, and time window identical, change nothing but the pool, and let each run go long enough that the block pattern actually shows up. A small honest test beats a large vendor promise every time. Track these for each pool:
- Kept rows
- 403 or captcha rate
- Median response time
- GB used
- Retries per success
Default decision
As a starting point, reach for Volume Residential on public, forgiving targets where retries are cheap and blocks are rare. Move up to Premium only once the same controlled test shows it earning its keep through fewer blocks, fewer retries, or a lower cost per kept result. Let the measurement pull you toward the upgrade rather than the marketing.
A simple bakeoff worksheet
Put both pools through the same target with request count, time window, country, headers, and retry policy held identical, then reduce each run to a single comparable number:
cost_per_kept_result = gb_used * price_per_gb / kept_resultsPlug in the real prices and the trade-off becomes concrete. At $0.89/GB, Volume only stays cheaper while its retry rate stays low; if Premium at $5.00/GB halves the retries and blocks on a hard target, it can come out ahead per kept row despite the higher unit price. When Volume already keeps the data cleanly, though, Premium is just a more expensive habit.
| Metric | Why it matters |
|---|---|
| Kept results | Measures useful output. |
| GB used | Measures real cost. |
| Retry rate | Shows hidden waste. |
| Block rate | Shows target fit. |
A common false win
Volume Residential often looks cheaper in a short test simply because the first few requests sail through. The bill catches up later, when concurrency rises, retries kick in, and blocked pages get re-downloaded again and again. Premium can look indefensibly expensive right up until you measure the same job under that load.
So run the bakeoff at the concurrency you actually plan to use, because a pool that behaves at one worker can fall apart at twenty. Cost per kept result is only meaningful when it carries the load level baked in, not just the comfort of the first successful request.
Test on the target that decides the budget
One rule does more than any other to keep this honest: do not run the bakeoff on your easiest target. Use the one that actually drives the buying decision, the page where most of the money gets spent, because a Premium pool that only beats Volume on a target you barely touch is no reason to overhaul the whole setup. The winning pool has to win where the spend lives.
And the answer has a shelf life. Scrape results age badly as targets tighten their rules, so when a major site changes its defenses, re-run the comparison rather than trusting last quarter's numbers. Keep both samples on file and track each pool's failures separately, so the next decision starts from evidence instead of memory.
Residential pool FAQ
When is premium worth it? When it lowers block rate or retry count enough to reduce cost per kept result. Premium pools tend to draw IPs with cleaner reputations on blocklist registries such as Spamhaus, which is one reason hard targets accept them at higher rates.
When is volume enough? When the target is public, forgiving, and cheap to retry.
What metric wins? Cost per kept result, not sticker price or pool size.