szetszwo commented on PR #6613: URL: https://github.com/apache/ozone/pull/6613#issuecomment-3482119540
> I still have reservations that the chatty nature of the client having to request each piece of the block will add latency and overhead we don't need limiting any potential performance gains, especially with the size of reads I have seen when testing from the haoop shell and spark. This is for avoiding the deadlock but not the performance. > > BTW, how large is enough? Would it slows down other operations for creating such a large handler pool? > I don't know, but I have seen HDFS work just fine with 32k threads active, provided the open file limits are high enough. So, we have to start 32k threads for each client? It does not sound right. (Sorry that I missed your reply previously.) -- 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]
