jolausa

vsperf results tails

Jul 24th, 2018
196
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 9.66 KB | None | 0 0
  1. (vsperfenv) tails-1:~/vswitchperf # cat /tmp/results_2018-07-24_05-25-07/OvsVanilla_test_report.rst
  2. ============================================================
  3. Performance report for OvsVanilla
  4. ============================================================
  5.  
  6. .. This work is licensed under a Creative Commons Attribution 4.0 International License.
  7. .. http://creativecommons.org/licenses/by/4.0
  8. .. (c) OPNFV, Intel Corporation, AT&T and others.
  9.  
  10. Introduction
  11. ============
  12. The objective of the OPNFV project titled **"Characterise vSwitch Performance
  13. for Telco NFV Use Cases"**, is to evaluate a virtual switch to identify its
  14. suitability for a Telco Network Function Virtualization (NFV) environment. As
  15. well as this, the project aims to identify any gaps or bottlenecks in order to
  16. drive architectural changes to improve virtual switch performance and
  17. determinism. The purpose of this document is to summarize the results of the
  18. tests carried out on the virtual switch in the Network Function Virtualization
  19. Infrastructure (NFVI) and, from these results, provide evaluations and
  20. recommendations for the virtual switch. Test results will be outlined in
  21. details-of-LTR_, preceded by the document-identifier_ and the scope_ and
  22. references_).
  23.  
  24. This document is currently in draft form.
  25.  
  26. .. _document-identifier:
  27.  
  28. Document identifier
  29. -------------------
  30. The document id will be used to uniquely identify versions of the LTR. The
  31. format for the document id will be:
  32. OPNFV\_vswitchperf\_LTR\_rel\_STATUS, the status is one of: DRAFT, REVIEWED,
  33. CORRECTED or FINAL. The document id for this version of the LTR is:
  34. OPNFV\_vswitchperf\_LTR\_Brahmaputra\_DRAFT.
  35.  
  36. .. _scope:
  37.  
  38. Scope
  39. -----
  40. The scope of this report is to detail the results of the tests that have been
  41. performed on the virtual switch. This report will also evaluate the results of
  42. these tests and, based on these evaluations, provide recommendations on the
  43. suitability of the virtual switch for use in a Telco NFV environment.
  44.  
  45. .. _references:
  46.  
  47. References
  48. ----------
  49. `OPNFV_vswitchperf_LTD_Brahmaputra_REVIEWED
  50. <http://artifacts.opnfv.org/vswitchperf/docs/requirements/vswitchperf_ltd.html>`__
  51.  
  52. .. _details-of-LTR:
  53.  
  54. Details of the Level Test Report
  55. ================================
  56. This section provides a test-results-overview_. Also included are the rationale_
  57. and the conclusions_.
  58.  
  59. .. _test-results-overview:
  60.  
  61.  
  62.  
  63. Test ID: PHY2PHY_TPUT
  64. --------------------------
  65.  
  66. Test Environment
  67. ~~~~~~~~~~~~~~~~
  68. Below is the environment that the test was performed in:
  69.  
  70. * OS: SLES 15
  71. * Kernel Version: 4.12.14-23-default
  72. * NIC(s):
  73. * Mellanox Technologies MT27800 Family [ConnectX-5]
  74. * Mellanox Technologies MT27800 Family [ConnectX-5]
  75. * Board: Supermicro X10SRL-F [1 sockets]
  76. * CPU: Intel(R) Xeon(R) CPU E5-2650 v4 @ 2.20GHz
  77. * CPU cores: 24
  78. * Memory: 65588600 kB
  79. * Virtual Switch Set-up: p2p
  80. * vswitchperf: GIT tag: 50f5064b274626e030f3584a17c95ef02d8f4a07
  81. * Traffic Generator: Trex, Version: v2.38, GIT tag: dc557baa2deb271e757677f0c15abdd89e4ecb77
  82. * vSwitch: OvsVanilla, Version: 2.8.2, GIT tag: None
  83.  
  84. Below are test details:
  85.  
  86. * Test ID: phy2phy_tput
  87. * Description: LTD.Throughput.RFC2544.PacketLossRatio
  88. * Deployment: p2p
  89. * Traffic type: rfc2544_throughput
  90. * Bidirectional : True
  91.  
  92. Test results for packet size: 64
  93. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  94. A detailed summary of the main results is outlined below.
  95.  
  96. Results/Metrics Collected
  97. ^^^^^^^^^^^^^^^^^^^^^^^^^
  98.  
  99. The following are the metrics obtained during this test:
  100.  
  101. ========================== ==================================
  102. Metric Result
  103. ========================== ==================================
  104. tx_frames 57221414
  105. rx_frames 57221414
  106. tx_rate_fps 1906629.800
  107. throughput_rx_fps 1906629.600
  108. tx_rate_mbps 976.201
  109. throughput_rx_mbps 976.194
  110. tx_rate_percent Unknown
  111. throughput_rx_percent Unknown
  112. frame_loss_percent 0.000
  113. min_latency_ns 2.000
  114. max_latency_ns 151.000
  115. avg_latency_ns 60.440
  116. type rfc2544_throughput
  117. packet_size 64
  118. vswitch OvsVanilla
  119. traffic_type udp
  120. test_execution_time 00:20:06
  121. start_time 2018-07-24 05:25:07
  122. stop_time 2018-07-24 05:45:14
  123. ========================== ==================================
  124.  
  125. Statistics collected
  126. ^^^^^^^^^^^^^^^^^^^^
  127.  
  128. The following system statistics were collected during testcase execution:
  129.  
  130. ========================== ==================================
  131. Process: ovs-vswitchd
  132. -------------------------------------------------------------
  133. Statistic Value
  134. ========================== ==================================
  135. %usr 0.20
  136. %system 0.38
  137. %guest 0.00
  138. %wait 0.00
  139. %CPU 0.56
  140. CPU -
  141. minflt/s 0.16
  142. majflt/s 0.00
  143. VSZ 1906428
  144. RSS 13720
  145. %MEM 0.02
  146. kB_rd/s 0.00
  147. kB_wr/s 0.01
  148. kB_ccwr/s 0.00
  149. iodelay 0
  150. ========================== ==================================
  151.  
  152.  
  153. ========================== ==================================
  154. Process: ovsdb-server
  155. -------------------------------------------------------------
  156. Statistic Value
  157. ========================== ==================================
  158. %usr 0.01
  159. %system 0.00
  160. %guest 0.00
  161. %wait 0.00
  162. %CPU 0.01
  163. CPU -
  164. minflt/s 0.01
  165. majflt/s 0.00
  166. VSZ 60472
  167. RSS 8096
  168. %MEM 0.01
  169. kB_rd/s 0.00
  170. kB_wr/s 0.00
  171. kB_ccwr/s 0.00
  172. iodelay 0
  173. ========================== ==================================
  174.  
  175.  
  176.  
  177. Anomalies
  178. ~~~~~~~~~~
  179. No anomalies were detected during the course of this test.
  180.  
  181. Testing Activities/Events
  182. ~~~~~~~~~~~~~~~~~~~~~~~~~
  183. pidstat is used to collect the process statistics, as such some values such as
  184. %CPU and %USER maybe > 100% as the values are summed across multiple cores. For
  185. more info on pidstat please see: http://linux.die.net/man/1/pidstat. Please
  186. note that vsperf recalculates the CPU consumption of a process by aggregating
  187. the CPU usage of each thread.
  188.  
  189. Known issues: Some reported metrics have the value "unkown". These values are
  190. marked unknown as they are not values retrieved from the external tester
  191. (traffic generator). They were incorrectly derived in a way that made assumptions
  192. about packet sizes, as such they have been deprecated from vsperf and marked as
  193. unknown. They will be resolved in the next release.
  194.  
  195. .. There must be blank lines around to ensure correct formatting.
  196.  
  197. .. This work is licensed under a Creative Commons Attribution 4.0 International License.
  198. http://creativecommons.org/licenses/by/4.0
  199.  
  200. .. _rationale:
  201.  
  202. Rationale for decisions
  203. =======================
  204.  
  205. The tests conducted do not have pass/fail/conditional-pass criteria. The test
  206. is simply conducted and the results are reported.
  207.  
  208. .. _conclusions:
  209.  
  210. Conclusions and recommendations
  211. ===============================
  212.  
  213. The test results are stable. The vsperf CI jobs that were used to obtain the
  214. results can be found at https://wiki.opnfv.org/wiki/vsperf_results.
  215.  
  216. General
  217. ========
  218.  
  219. Glossary
  220. --------
  221.  
  222. - NFV - Network Function Virtualization
  223. - Mbps - 1,000,000bps
  224.  
  225. Document change procedures and history
  226. --------------------------------------
  227.  
  228. =============================================== ================= =============
  229. Document ID Author Date Modified
  230. =============================================== ================= =============
  231. `OPNFV_vswitchperf_LTR_ver_1.0_Jan_15_CN_DRAFT` Christopher Nolan 23/01/2015
  232. `OPNFV_vswitchperf_LTR_ver_1.1_Jan_15_CN_DRAFT` Christopher Nolan 28/01/2015
  233. =============================================== ================= =============
Advertisement
Add Comment
Please, Sign In to add comment