ivandika3 opened a new pull request, #10571: URL: https://github.com/apache/ozone/pull/10571
## What changes were proposed in this pull request? We found that the CPU time of createPipelineForRead during high read traffic is mostly spent waiting on the SecureRandom monitor lock during the UUID random generation. SecureRandom is static and requires therefore lock should be static. Since the SecureRandom is static, it also contends with all other UUID generation and can affect performance (as per Amdahl's law). I don't think it is required to use SecureRandom for read pipeline ID since the read pipeline ID is not sensitive (AFAIK it's throwaway ID) and predicting the next read pipeline ID should not have any security implication ## What is the link to the Apache JIRA https://issues.apache.org/jira/browse/HDDS-15602 ## How was this patch tested? CI -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
