[
https://issues.apache.org/jira/browse/HDDS-8897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17737048#comment-17737048
]
Attila Doroszlai commented on HDDS-8897:
----------------------------------------
Thanks [~Nicholas Niu] for collecting profiler data.
>From the lock profile it seems lock contention is not a problem with this
>workload, less than 1% comes from {{WritableECContainerProvider#getContainer}}.
According to the CPU profile, {{WritableECContainerProvider#getContainer}}
takes 10.91%, of which 40% (absolute value 4.36%) is spent in
{{getMaximumPipelines}}. This has been improved in HDDS-8906 and HDDS-8907
recently. (Based on the stream pipelines in your profile this was running code
prior to those changes.)
> ec container has too high latency when allocate blocks
> ------------------------------------------------------
>
> Key: HDDS-8897
> URL: https://issues.apache.org/jira/browse/HDDS-8897
> Project: Apache Ozone
> Issue Type: Improvement
> Reporter: GuoHao
> Assignee: Stephen O'Donnell
> Priority: Blocker
> Labels: pull-request-available
> Attachments: image-2023-06-21-21-58-15-052.png,
> image-2023-06-21-21-58-50-518.png, image-2023-06-26-16-22-38-253.png,
> image-2023-06-26-16-23-01-567.png, profile-scm-60s-cpu.svg,
> profile-scm-60s-lock.svg
>
>
> ec container has too high latency when allocate blocks
>
> I use ec in a high concurrency situation, I configure the metric on scm, and
> as concurrency gradually increases, the latency of the allocate block
> increases.
>
> allocate block ops：
> !image-2023-06-21-21-58-50-518.png!
>
> average latency：
> !image-2023-06-21-21-58-15-052.png!
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
