- - **[Overview](methodology/overview)**: Terminology, per-thread
- resources, multi-core speedup, VPP forwarding modes and DUT state
- considerations.
- - **[Measurement](methodology/measurements)**: Data plane throughput, packet
- latency and the telemetry.
- - **[Test](methodology/test)**: Methodology of all tests used in CSIT.
- - **[Trending](methodology/trending)**: A high-level design of a system for
- continuous performance measuring, trending and change detection for FD.io
- VPP SW data plane (and other performance tests run within CSIT
- sub-project).
- - **[Per-patch Testing](methodology/per_patch_testing)**: A methodology
- similar to trending analysis is used for comparing performance before a DUT
- code change is merged.
+ - **[Overview]({{< relref "/methodology/overview/" >}})**: Terminology,
+ per-thread resources, multi-core speedup, VPP forwarding modes and DUT
+ state considerations.
+ - **[Measurement]({{< relref "/methodology/measurements/" >}})**: Data plane
+ throughput, packet latency and the telemetry.
+ - **[Test]({{< relref "/methodology/test/" >}})**: Methodology of all tests
+ used in CSIT.
+ - **[Trending]({{< relref "/methodology/trending/" >}})**: A high-level
+ design of a system for continuous performance measuring, trending and
+ change detection for FD.io VPP SW data plane (and other performance tests
+ run within CSIT sub-project).
+ - **[Per-patch Testing]({{< relref "/methodology/per_patch_testing" >}})**:
+ A methodology similar to trending analysis is used for comparing
+ performance before a DUT code change is merged.