Skip to content

Edge Constrained Evaluation Results

MarianaGarcez edited this page Jan 9, 2026 · 4 revisions

Edge Constrained Evaluation Results

To validate the edge deployability of MobilityNebula, we test our implementation under strict container resource caps in Docker.

We implement the nine queries (for supported queries per system) in:

All systems are evaluated with the same TCP stream input workload of 20k events/s. During these tests, we measure CPU usage, memory usage, throughput, and latency. Each query runs for 30 seconds.

We tested multiple configurations on a single-node setup under three memory caps: 512 MB, 2 GB, and 8 GB of RAM. We utilized:

  • 4 vCPU + 8 GB RAM to simulate a Raspberry Pi 5
  • 2 vCPU + 8 GB RAM to simulate an nROK device

Furthermore, we evaluated the conditions under which queries were either terminated or timed out without producing any sink output.

Throughput under Resource Caps

Input Throughput vs Memory

2_throughput_vs_memory

Input Throughput vs vCPU

1_throughput_vs_vcpu

Latency under Resource Caps

P95 Latency vs Memory Configuration (Successful Queries)

8_latency_vs_memory

CPU Usage per Query

Avg CPU Usage per Query (512m RAM, 1 vCPU)

5_cpu_usage_512m_1vcpu

Avg CPU Usage per Query (2g RAM, 1 vCPU)

9_cpu_usage_2g_1vcpu

Avg CPU Usage per Query (8g RAM, 2 vCPU)

3_cpu_usage_per_query

Avg CPU Usage per Query (8g RAM, 4 vCPU)

11_cpu_usage_8g_4vcpu

Memory Usage per Query

Peak Memory Usage per Query (512m RAM, 1 vCPU)

6_memory_usage_512m_1vcpu

Peak Memory Usage per Query (2g RAM, 1 vCPU)

10_memory_usage_2g_1vcpu

Peak Memory Usage per Query (8g RAM, 2 vCPU)

4_memory_usage_per_query

Peak Memory Usage per Query (8g RAM, 4 vCPU)

12_memory_usage_8g_4vcpu