> For the complete documentation index, see [llms.txt](https://docs.thousandeyes.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.thousandeyes.com/product-documentation/connected-devices/device-agents/validation-and-troubleshooting/speed-quick-wins.md).

# Speed Quick Wins

Use these checks when the agent measures below the expected tier. Run them in order and keep the results.

{% hint style="warning" %}
**Point-to-Point Protocol over Ethernet (PPPoE) Can Affect Speed Results**

If the WAN uses PPPoE, record it before comparing results. PPPoE can add significant per-packet CPU cost when the kernel or driver lacks suitable Generic Receive Offload (GRO) or Generic Segmentation Offload (GSO) support for PPPoE. Compare results on the same device over a temporary non-PPPoE WAN when possible.
{% endhint %}

## 1. Comparing Normal and On-Net Results

Run the agent in self-test mode with its normal target and save the result. Then set up an [on-net test server](https://docs.thousandeyes.com/product-documentation/connected-devices/device-agents/on-net-test-server-installation.md) and repeat the self-test against it with a [target override](https://docs.thousandeyes.com/product-documentation/connected-devices/device-agents/validation-and-troubleshooting/validate-with-self-test-mode.md#running-self-test-against-an-on-net-server).

An on-net test removes the public internet path and remote target capacity from the comparison.

| Result                                                           | Next focus                                                |
| ---------------------------------------------------------------- | --------------------------------------------------------- |
| The on-net result reaches the tier, but the normal result is low | Wider network path or remote target capacity              |
| Both results are low                                             | Device network stack, agent backend, acceleration, or CPU |
| Only upload or download is low                                   | Direction-specific offload or queue handling              |

## 2. Checking the Speed Backend

Read `Speed backend` in the [self-test output](https://docs.thousandeyes.com/product-documentation/connected-devices/device-agents/validation-and-troubleshooting/validate-with-self-test-mode.md). A hardware backend means the agent used acceleration for that iteration. `software` means the agent used the software path.

See [System Requirements](https://docs.thousandeyes.com/product-documentation/connected-devices/device-agents/getting-started/system-requirements.md#hardware-acceleration) for supported accelerators and their prerequisites. If a supported accelerator is expected but self-test reports `software`, confirm the target board support package (BSP) and required device nodes or utilities before changing other settings.

## 3. Checking CPU Use by Direction

While the agent runs in self-test mode to measure upload and download, run `top`.

| Observation                               | Check next                                                                               |
| ----------------------------------------- | ---------------------------------------------------------------------------------------- |
| Download is low and one core is saturated | GRO, receive queues, Receive Side Scaling (RSS), and Receive Packet Steering (RPS)       |
| Upload is low and one core is saturated   | GSO, TCP Segmentation Offload (TSO), transmit queues, and Transmit Packet Steering (XPS) |
| All cores are saturated                   | Whether the expected hardware acceleration backend is active                             |

## 4. Troubleshooting Offloads and Queues

### Inspecting Offloads and Queues

Find the WAN interface:

```bash
ip route show default
```

Replace `eth0` below with the interface shown after `dev`:

```bash
ethtool -k eth0 | grep -E 'generic-receive-offload|generic-segmentation-offload|tcp-segmentation-offload'
ls -1 /sys/class/net/eth0/queues
```

Check for:

* GRO is disabled when download is low.
* GSO or TSO is disabled when upload is low.
* A device expected to distribute network processing across CPUs has only one receive or transmit queue.

An offload marked `[fixed]` in `ethtool` cannot be changed with `ethtool`. Address missing queue or offload support in the device driver, BSP, or firmware.

### Testing a Supported Offload Change

If `ethtool` reports that GRO, GSO, or TSO is supported but disabled, record the current values. Enable only the setting that matches the affected direction. For example:

```bash
ethtool -K eth0 gro on
```

Use `gso on` or `tso on` instead when testing upload. Rerun the same on-net self-test and compare the result.

Treat this as a diagnostic change. Restore the original value after the comparison. If the change consistently improves the result without affecting other traffic, add it to the device's firmware or BSP. Then repeat the full device QA and rollout process.

If a confirmed platform optimization must apply only during an HTTP speed test, see [Speed-Test Optimization Hooks](https://docs.thousandeyes.com/product-documentation/connected-devices/device-agents/validation-and-troubleshooting/speed-test-optimization-hooks.md). Before using hooks, confirm that the installed agent package supports speed-test hooks. Evaluate one optimization at a time, and check both cleanup and throughput. For TCP speed-test validation, see [TCP Speed Tests](https://docs.thousandeyes.com/product-documentation/connected-devices/device-agents/configuration/tcp-speed-tests.md).

## If the Result Is Still Low

When you contact support, include:

* Complete self-test output and raw speed result lines.
* Unit ID, device model, system-on-a-chip (SoC), firmware, and kernel versions.
* Upload and download results against normal and on-net targets.
* WAN protocol and round-trip time.
* `top`, `ethtool -k`, and queue output from the checks above.
* Changes already tried and their results.

Do not publish a production image with unverified network stack changes.
