summaryrefslogtreecommitdiffstats
path: root/docs/whatisvpp/performance.rst
diff options
context:
space:
mode:
authorNathan Skrzypczak <nathan.skrzypczak@gmail.com>2021-08-19 11:38:06 +0200
committerDave Wallace <dwallacelf@gmail.com>2021-10-13 23:22:32 +0000
commit9ad39c026c8a3c945a7003c4aa4f5cb1d4c80160 (patch)
tree3cca19635417e28ae381d67ae31c75df2925032d /docs/whatisvpp/performance.rst
parentf47122e07e1ecd0151902a3cabe46c60a99bee8e (diff)
docs: better docs, mv doxygen to sphinx
This patch refactors the VPP sphinx docs in order to make it easier to consume for external readers as well as VPP developers. It also makes sphinx the single source of documentation, which simplifies maintenance and operation. Most important updates are: - reformat the existing documentation as rst - split RELEASE.md and move it into separate rst files - remove section 'events' - remove section 'archive' - remove section 'related projects' - remove section 'feature by release' - remove section 'Various links' - make (Configuration reference, CLI docs, developer docs) top level items in the list - move 'Use Cases' as part of 'About VPP' - move 'Troubleshooting' as part of 'Getting Started' - move test framework docs into 'Developer Documentation' - add a 'Contributing' section for gerrit, docs and other contributer related infos - deprecate doxygen and test-docs targets - redirect the "make doxygen" target to "make docs" Type: refactor Change-Id: I552a5645d5b7964d547f99b1336e2ac24e7c209f Signed-off-by: Nathan Skrzypczak <nathan.skrzypczak@gmail.com> Signed-off-by: Andrew Yourtchenko <ayourtch@gmail.com>
Diffstat (limited to 'docs/whatisvpp/performance.rst')
-rw-r--r--docs/whatisvpp/performance.rst70
1 files changed, 0 insertions, 70 deletions
diff --git a/docs/whatisvpp/performance.rst b/docs/whatisvpp/performance.rst
deleted file mode 100644
index d7af24a3909..00000000000
--- a/docs/whatisvpp/performance.rst
+++ /dev/null
@@ -1,70 +0,0 @@
-.. _performance:
-
-Performance
-===========
-
-One of the benefits of FD.io VPP is it's high performance on relatively low-power computing.
-Included are the following.
-
-* A high-performance user-space network stack designed for commodity hardware:
-
- - L2, L3 and L4 features and encapsulations.
-
-* Optimized packet interfaces supporting a multitude of use cases:
-
- - An integrated vhost-user backend for high speed VM-to-VM connectivity
- - An integrated memif container backend for high speed Container-to-Container connectivity
- - An integrated vhost based interface to punt packets to the Linux Kernel
-
-* The same optimized code-paths run execute on the host, and inside VMs and Linux containers
-* Leverages best-of-breed open source driver technology: `DPDK <https://www.dpdk.org/>`_
-* Tested at scale; linear core scaling, tested with millions of flows and mac addresses
-
-These features have been designed to take full advantage of common micro-processor optimization techniques, such as:
-
-* Reducing cache and TLS misses by processing packets in vectors
-* Realizing `IPC <https://en.wikipedia.org/wiki/Instructions_per_cycle>`_ gains with vector instructions such as: SSE, AVX and NEON
-* Eliminating mode switching, context switches and blocking, to always be doing useful work
-* Cache-lined aligned buffers for cache and memory efficiency
-
-
-Continuous System Integration and Testing (CSIT)
-------------------------------------------------
-
-The Continuous System Integration and Testing (CSIT) project provides functional and performance
-testing for FD.io VPP. This testing is focused on functional and performance regressions. The results
-are posted to `CSIT Test Report <https://docs.fd.io/csit/master/report/>`_.
-
-For more about CSIT checkout the following links:
-
-* `CSIT Code Documentation <https://docs.fd.io/csit/master/doc/overview.html>`_
-* `CSIT Test Overview <https://docs.fd.io/csit/master/report/introduction/overview.html>`_
-* `VPP Performance Dashboard <https://docs.fd.io/csit/master/trending/introduction/index.html>`_
-
-
-CSIT Packet Throughput examples
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-
-Following are pointers to a few of the CSIT test reports. The test's titles read like this:
-
-<packet size>-<number of threads><number of cores>-<test>-<interface type>
-
-For example the test with the title 64b-2t1c-l2switching-base-i40e is the
-test that does l2 switching using 64 byte packets, 2 threads, 1 core using an i40e
-interface.
-
-Here are a few examples:
-
-* `L2 Ethernet switching <https://docs.fd.io/csit/master/report/vpp_performance_tests/packet_throughput_graphs/l2.html>`_
-* `IPv4 Routing <https://docs.fd.io/csit/master/report/vpp_performance_tests/packet_throughput_graphs/ip4.html>`_
-* `IPv6 Routing <https://docs.fd.io/csit/master/report/vpp_performance_tests/packet_throughput_graphs/ip6.html>`_
-
-
-Trending Throughput Graphs
-^^^^^^^^^^^^^^^^^^^^^^^^^^
-
-These are some of the trending packet throughput graphs from the CSIT `trending dashboard <https://docs.fd.io/csit/master/trending/introduction/index.html>`_. **Please note that**, performance in the trending graphs will change on a nightly basis in line with the software development cycle:
-
-* `L2 Ethernet Switching Trending <https://docs.fd.io/csit/master/trending/trending/l2.html>`_
-* `IPv4 Routing Trending <https://docs.fd.io/csit/master/trending/trending/ip4.html>`_
-* `IPv6 Routing Trending <https://docs.fd.io/csit/master/trending/trending/ip6.html>`_