Difference between revisions of "Project Proposals/CSIT"
Mackonstan (Talk | contribs) |
Mackonstan (Talk | contribs) |
||
Line 3: | Line 3: | ||
== Name == | == Name == | ||
− | + | Performance Measurement and Analysis Tools | |
− | + | ||
− | + | ||
== Project Contact Name and Email == | == Project Contact Name and Email == | ||
− | < | + | Patrick Lu <patrick.lu@intel.com> |
− | + | ||
− | + | ||
== Repository Name == | == Repository Name == | ||
− | + | pma_tools | |
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
== Description == | == Description == | ||
− | + | pma_tools project aims to develop software tools for performance and efficiency measurements of compute optimized network data plane applications like FD.io VPP (and similar) while running on compute platform(s) . pma_tools will provide tools that enable systematic measurement methodologies of such applications and are to be directly integrated within the FD.io operating environment(s) and FD.io projects like VPP, CSIT and TRex using developed APIs. This could facilitate further standardization of performance measurement and analysis methodologies for compute platforms running network workloads. | |
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
== Scope == | == Scope == | ||
− | + | Project initial target development areas include: | |
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | * Automation tooling with python interface (API) for packet traffic generation (e.g. Ixia) and throughput benchmark test definitions, life-cycle management and granular measurement data analytic. | |
− | + | * A set of scripts to create Ubuntu live image with benchmark-centric customizations (pre-installed benchmarks and library dependencies). | |
− | + | ** The identical image will be able to deploy in various test environments, such as bare-metal, VM setup. This enable a consistent and calibrated environment for performance testing. | |
− | + | * Tools to calibrate OS level CPU “jitter” (CPU core context switching) introduced by kernel- and other user-space tasks. | |
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
== Initial Committers == | == Initial Committers == | ||
− | + | * [mailto:patrick.lu@intel.com Patrick Lu], LF-ID: yplu. | |
− | + | * [mailto:georgii.tkachuk@intel.com George Tkachuk], LF-ID: tbc. | |
− | + | * [mailto:subhiksha.ravisundar@intel.com Subhiksha Ravisundar], LF-ID: tbc. | |
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | * [mailto: | + | |
− | * [mailto: | + | |
− | * [mailto: | + | |
* [mailto:mkonstan@cisco.com Maciek Konstantynowicz], LF-ID: mackonstan. | * [mailto:mkonstan@cisco.com Maciek Konstantynowicz], LF-ID: mackonstan. | ||
− | * [mailto: | + | * [mailto:pmikus@cisco.com Peter Mikus] LF-ID: pmikus. |
− | + | ||
== Vendor Neutral == | == Vendor Neutral == | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
No current or expected issues with vendor neutrality. | No current or expected issues with vendor neutrality. | ||
== Meets Board Policy (including IPR, being within Board defined Scope etc) == | == Meets Board Policy (including IPR, being within Board defined Scope etc) == | ||
− | Meets board policy as expressed in [https://fd.io/sites/cpstandard/files/pages/files/exhibit_c_-_fd.io_technical_community_charter.pdf Technical Community Charter] and [https://fd.io/sites/cpstandard/files/pages/files/exhibit_b_-_fd.io_ip_policy.pdf IP Policy] | + | Meets board policy as expressed in [https://fd.io/sites/cpstandard/files/pages/files/exhibit_c_-_fd.io_technical_community_charter.pdf Technical Community Charter] and [https://fd.io/sites/cpstandard/files/pages/files/exhibit_b_-_fd.io_ip_policy.pdf IP Policy] |
− | + | ||
− | + | ||
− | [https:// | + | == Administrata == |
+ | * Request for Project proposal consideration | ||
+ | ** Email: (place link to email to TSC proposing project, this can be obtained from [https://lists.fd.io/pipermail/tsc/ TSC Archives] | ||
+ | ** Date: (date proposed, makes it simpler to calculate the pre-requisite 2 week time period of gestation before being permitted to be voted on) |
Latest revision as of 20:15, 23 October 2017
Contents
Name
Performance Measurement and Analysis Tools
Project Contact Name and Email
Patrick Lu <patrick.lu@intel.com>
Repository Name
pma_tools
Description
pma_tools project aims to develop software tools for performance and efficiency measurements of compute optimized network data plane applications like FD.io VPP (and similar) while running on compute platform(s) . pma_tools will provide tools that enable systematic measurement methodologies of such applications and are to be directly integrated within the FD.io operating environment(s) and FD.io projects like VPP, CSIT and TRex using developed APIs. This could facilitate further standardization of performance measurement and analysis methodologies for compute platforms running network workloads.
Scope
Project initial target development areas include:
- Automation tooling with python interface (API) for packet traffic generation (e.g. Ixia) and throughput benchmark test definitions, life-cycle management and granular measurement data analytic.
- A set of scripts to create Ubuntu live image with benchmark-centric customizations (pre-installed benchmarks and library dependencies).
- The identical image will be able to deploy in various test environments, such as bare-metal, VM setup. This enable a consistent and calibrated environment for performance testing.
- Tools to calibrate OS level CPU “jitter” (CPU core context switching) introduced by kernel- and other user-space tasks.
Initial Committers
- Patrick Lu, LF-ID: yplu.
- George Tkachuk, LF-ID: tbc.
- Subhiksha Ravisundar, LF-ID: tbc.
- Maciek Konstantynowicz, LF-ID: mackonstan.
- Peter Mikus LF-ID: pmikus.
Vendor Neutral
No current or expected issues with vendor neutrality.
Meets Board Policy (including IPR, being within Board defined Scope etc)
Meets board policy as expressed in Technical Community Charter and IP Policy
Administrata
- Request for Project proposal consideration
- Email: (place link to email to TSC proposing project, this can be obtained from TSC Archives
- Date: (date proposed, makes it simpler to calculate the pre-requisite 2 week time period of gestation before being permitted to be voted on)