Performance Analysis of HTTP Reverse Proxies LEO Constellation

Performance Analysis of HTTP Reverse Proxies over LEO Constellation

Implementation plan:

Scenario 1 : Baseline Performance

Step 1: Initially, we constructed the network using 3 LEO Satellites, 3 Terminals, 3 ForwarderProxy Servers, User number of Clients, 3 GroundStations, 1 ReverseProxy Server, and 5 Servers.

(ideal conditions with 100 ms latency, 50 Mbps bandwidth and 1 GB cache (LRU))

Step 2: Then, we simulate and collect network data such as positions, packet send/receive, packet size, transmission time, transmit power, path loss, distance, delay, jitter, and packet loss.

Step 3: Next, we analyze the baseline network performance without caching using the collected data.

Step 4: Next, we analyze different caching strategies, workload variation and content popularity based on collected network data.

Step 5: Next, we optimize cache operations using predictive caching and prefetching techniques.

Step 6: Finally, we plot performance for the following metrics:

6.1: Number of Satellites vs. Latency (ms)
6.2: Number of Satellites vs. Response Time (ms)
6.3: Number of Servers vs. Load Distribution (%)
6.4: Number of Clients vs. Cache Hit Rate (%)
6.5: Number of Clients vs. Throughput (Mbps)

Scenario 2 : (High Latency Impact)

Step 1: Initially, we constructed the network using 3 LEO Satellites, 3 Terminals, 3 ForwarderProxies,n number of Clients, 3 GroundStations, 1 ReverseProxy, and 5 Servers.

(higher satellite latency (600–1200 ms), 10 Mbps bandwidth, 1% packet loss, 1 GB cache (LRU))

Step 2: Then, we simulate and collect network data such as positions, packet send/receive, packet size, transmission time, transmit power, path loss, distance, delay, jitter, and packet loss.

Step 3: Next, we analyze the baseline network performance without caching using the collected data.

Step 4: Next, we analyze different caching strategies, workload variation and content popularity based on collected network data.

Step 5: Next, we optimize cache operations using predictive caching and prefetching techniques.

Step 6: Finally, we plot performance for the following metrics:

6.1: Number of Satellites vs. Latency (ms)
6.2: Number of Satellites vs. Response Time (ms)
6.3: Number of Servers vs. Load Distribution (%)
6.4: Number of Clients vs. Cache Hit Rate (%)
6.5: Number of Clients vs. Throughput (Mbps)

Scenario 3 : (Bandwidth Constraints)

Step 1: Initially, we constructed the network using 3 LEO Satellites, 3 Terminals, 3 ForwarderProxies, n number of Clients, 3 GroundStations, 1 ReverseProxy, and 5 Servers.

(bandwidth (1–10 Mbps), 600 ms latency1 GB cache (LRU))

Step 2: Then, we simulate and collect network data such as positions, packet send/receive, packet size, transmission time, transmit power, path loss, distance, delay, jitter, and packet loss.

Step 3: Next, we analyze the baseline network performance without caching using the collected data.

Step 4: Next, we analyze different caching strategies, workload variation and content popularity based on collected network data.

Step 5: Next, we optimize cache operations using predictive caching and prefetching techniques.

Step 6: Finally, we plot performance for the following metrics:

6.1: Number of Satellites vs. Latency (ms)
6.2: Number of Satellites vs. Response Time (ms)
6.3: Number of Servers vs. Load Distribution (%)
6.4: Number of Clients vs. Cache Hit Rate (%)
6.5: Number of Clients vs. Throughput (Mbps)

Software Requirements:

1. Development Tool: OMNeT++ 4.6 or above
2. Operating System: Windows 10 (64-bit) or above

Note

1) If the proposed plan does not fully align with your requirements, please provide all necessary details—including steps, parameters, models, and expected outcomes—in advance. Kindly ensure that any missing configurations or specifications are clearly outlined in the plan before confirming, as post-implementation changes will not be accommodated.

2) If there’s no built-in solution for what the project needs, we can always turn to reference models, customize our own, different math models or write the code ourselves to fulfil the process.

3) If the plan satisfies your requirement, Please confirm with us.

4) Project based on Simulation only.

Related Pages