[ 
https://issues.apache.org/jira/browse/HDDS-8897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17735791#comment-17735791
 ] 

GuoHao edited comment on HDDS-8897 at 6/21/23 3:50 PM:
-------------------------------------------------------

[~sodonnell] 

Now the information I can give is:
1. the code I am using is ozone version 1.3.0
2. I am using scm without ha enabled, so I can exclude the raft synchronization 
overhead when creating and closing the pipeline.
3. I'm using the same workload and the latency is in the single digit ms level 
when allocate blocks for ratis 3 copies.


was (Author: nicholas niu):
[~sodonnell] 

 

Now the information I can give is:
1. the code I am using is ozone version 1.3.0
2. I am using scm without ha enabled, so I can exclude the raft synchronization 
overhead when creating and closing the pipeline.
3. I'm using the same workload and the latency is in the single digit ms level 
when allocate blocks for ratis 3 copies.

> 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
>         Attachments: image-2023-06-21-21-58-15-052.png, 
> image-2023-06-21-21-58-50-518.png
>
>
> 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]

Reply via email to