Skip to content

SAI API Performance Monitoring#2287

Merged
tjchadaga merged 1 commit into
opencomputeproject:masterfrom
JaiOCP:pmon
Jun 2, 2026
Merged

SAI API Performance Monitoring#2287
tjchadaga merged 1 commit into
opencomputeproject:masterfrom
JaiOCP:pmon

Conversation

@JaiOCP
Copy link
Copy Markdown
Contributor

@JaiOCP JaiOCP commented May 27, 2026

#2279 is the original PR. Code base got diverged.
This PR brings in support for measuring SAI API performance. This is based on presentation done in OCP 2023.

Signed-off-by: JaiOCP <jai.kumar@broadcom.com>
@tjchadaga
Copy link
Copy Markdown
Collaborator

/azp run

@azure-pipelines
Copy link
Copy Markdown

Azure Pipelines successfully started running 1 pipeline(s).

@tjchadaga
Copy link
Copy Markdown
Collaborator

@rck-innovium - please help sign off on this

@tjchadaga tjchadaga added the reviewed PR is discussed in SAI Meeting label May 28, 2026
@JaiOCP
Copy link
Copy Markdown
Contributor Author

JaiOCP commented May 29, 2026

@rck-innovium Can you please approve this PR or the old closed one (not sure if you can do that)



## 4.0 SAI Specification
New perfmon object is introduced. Each perfmon object specifies the object of interest, set of APIs and metrics to be measured for each API.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In the current model, SAI_PERFMON_ATTR_COMMON_API is of type sai_common_api_t and SAI_PERFMON_ATTR_PERFMON_METRICS is of type sai_perfmon_metrics_t. Similarly, SAI_PERFMON_ATTR_PERFDATA is a single u64.
These types are NOT lists. Hence, we need to reword that: Each perfmon object specifies the object type of interest, an API type and a metric to be measured.

@tjchadaga tjchadaga merged commit a876349 into opencomputeproject:master Jun 2, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

reviewed PR is discussed in SAI Meeting

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants