You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Wei-Chiu Chuang (Jira)" <ji...@apache.org> on 2026/10/20 19:54:00 UTC
[jira] [Commented] (HDDS-17184) Profile and benchmark Ozone CLI startup latency
[ https://issues.apache.org/jira/browse/HDDS-17184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18129314#comment-18129314 ]
Wei-Chiu Chuang commented on HDDS-17184:
----------------------------------------
cc: [~ayarovoy]
> Profile and benchmark Ozone CLI startup latency
> -----------------------------------------------
>
> Key: HDDS-17184
> URL: https://issues.apache.org/jira/browse/HDDS-17184
> Project: Apache Ozone
> Issue Type: Task
> Components: Ozone CLI
> Reporter: Wei-Chiu Chuang
> Assignee: Andrey Yarovoy
> Priority: Major
> Labels: cli, performance
>
> Establish baseline matrix: ozone version, ozone sh --help, ozone sh volume list (no cluster / with cluster), ozone admin, ozone interactive. Split *shell time* vs *Java time* (/usr/bin/time, time ozone …, optional OZONE_SHELL_TIMING / script markers). JVM: JFR or async-profiler cold start; sample -Xlog:class+load=info; compare jar count from ozone classpath ozone-cli-shell. Publish numbers + methodology in the Jira comment or a short dev doc section.
> Track cold-start / per-invocation overhead under HDDS-17183.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org