You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "JiangHua Zhu (Jira)" <ji...@apache.org> on 2021/07/05 03:44:00 UTC

[jira] [Created] (HDFS-16113) Improve CallQueueManager#swapQueue() execution performance

JiangHua Zhu created HDFS-16113:
-----------------------------------

             Summary: Improve CallQueueManager#swapQueue() execution performance
                 Key: HDFS-16113
                 URL: https://issues.apache.org/jira/browse/HDFS-16113
             Project: Hadoop HDFS
          Issue Type: Improvement
            Reporter: JiangHua Zhu


In CallQueueManager#swapQueue(), there are some codes:
CallQueueManager#swapQueue() {
......
while (!queueIsReallyEmpty(oldQ)) {}
......
}
In queueIsReallyEmpty():
......
for (int i = 0; i <CHECKPOINT_NUM; i++) {}
...
We found that this implementation has certain performance hindrances in real clusters.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org