Skip to content

Commit fa7616d

Browse files
Create new page and cross-link from ips-allocation
1 parent a3bf5c1 commit fa7616d

File tree

2 files changed

+17
-0
lines changed

2 files changed

+17
-0
lines changed

src/content/docs/aegis/about/ips-allocation.mdx

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -27,6 +27,8 @@ Refer to [connection forwarding](/aegis/about/connection-forwarding/) to underst
2727

2828
<Render file="concurrent-connections-explainer" />
2929

30+
Aegis also benefits from [connection reuse and connection coalescing](/aegis/about/reuse-and-coalescing/).
31+
3032
[GraphQL Analytics API](/aegis/analytics/) allows you to get visibility over Aegis IP utilization.
3133

3234
## Regional services
Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,15 @@
1+
---
2+
title: Connection reuse and coalescing
3+
pcx_content_type: concept
4+
sidebar:
5+
order: 4
6+
label: Reuse and coalescing
7+
---
8+
9+
Aside from [concurrent connections](/aegis/about/ips-allocation/#connections-to-your-origin)[^1], connection reuse and connection coalescing are also important concepts. They both have impact on latency and are considered when allocating your Aegis IPv4 addresses.
10+
11+
Implemented by HTTP/1.1, connection reuse describes multiple requests passing through one same connection (between one source IP:port and one destination IP:port). It is commonly the case even for simple websites nowadays.
12+
13+
With HTTP/2, requests can use the same connection even if they are for different domains.
14+
15+
[^1]: If you have one Aegis IP and two origins (A and B), this single Aegis IP can support 40,000 concurrent connections to origin A, while simultaneously supporting 40,000 concurrent connections to origin B.

0 commit comments

Comments
 (0)