 |
 |
Hi, I think that the places that may matter for what you mention are just the first two, i.e. inside XrdTPC (the other places are just related to the request header) Maybe Brian can comment on these two inside XrdTPC? Maybe just one would need to be changed. Cheers Fabrizio Il 12/10/2021 13:12, snafus ha scritto: > Hi @abh3 <https://github.com/abh3>, @bbockelm > <https://github.com/bbockelm> , @ffurano <https://github.com/ffurano>, > > I like to ask if a new (esoteric?) directive could be included to set > the size of the internal HTTP buffer size for 'normal' and tpc davs > transfers. > Currently it appears that there are hard-coded 1MiB buffers in the > XrdHttp and XrdTpc locations. > For RAL (with Echo, and it's Ceph object store), it would be very > helpful to be able to increase this to a some configurable sensible > multiple of this. > For read requests we can mitigate to some extent with a memcache proxy > and appropriate async sizes. > However for writes, I don't think we can do anything to make > improvements without code changes. > > From tests privately updating the code, this does show significant > improvements, but there may be some other implications (side effects, > etc.) I wouldn't be aware of. To have this as a configurable option in > the official codebase would give demonstrable improvements for us. > > Some of the locations I spotted (essentially reference 1024*1024) are: > https://github.com/xrootd/xrootd/blob/0e460d7a11702c9935ed9fc1c67f22cb998b6fa4/src/XrdTpc/XrdTpcStream.cc#L83 > <https://github.com/xrootd/xrootd/blob/0e460d7a11702c9935ed9fc1c67f22cb998b6fa4/src/XrdTpc/XrdTpcStream.cc#L83> > https://github.com/xrootd/xrootd/blob/70066fe7edaa68ea271ffdf9d54c9d26294eeafd/src/XrdTpc/XrdTpcTPC.cc#L29 > <https://github.com/xrootd/xrootd/blob/70066fe7edaa68ea271ffdf9d54c9d26294eeafd/src/XrdTpc/XrdTpcTPC.cc#L29> > https://github.com/xrootd/xrootd/blob/9b03713e40a98528e8736330ee40035281e78181/src/XrdHttp/XrdHttpProtocol.cc#L283 > <https://github.com/xrootd/xrootd/blob/9b03713e40a98528e8736330ee40035281e78181/src/XrdHttp/XrdHttpProtocol.cc#L283> > https://github.com/xrootd/xrootd/blob/db9bf87bf648b5af3a2bd30d55995e4212f684a2/src/XrdHttp/XrdHttpReq.cc#L1291 > <https://github.com/xrootd/xrootd/blob/db9bf87bf648b5af3a2bd30d55995e4212f684a2/src/XrdHttp/XrdHttpReq.cc#L1291> > https://github.com/xrootd/xrootd/blob/db9bf87bf648b5af3a2bd30d55995e4212f684a2/src/XrdHttp/XrdHttpReq.cc#L1296 > <https://github.com/xrootd/xrootd/blob/db9bf87bf648b5af3a2bd30d55995e4212f684a2/src/XrdHttp/XrdHttpReq.cc#L1296> > > Do you think this is something that can be accommodated? > Kind regards, > James > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub > <https://github.com/xrootd/xrootd/issues/1532>, or unsubscribe > <https://github.com/notifications/unsubscribe-auth/ABJBUT5QRVLWTFES7IO36LTUGQJ2BANCNFSM5F2J2QJA>. > Triage notifications on the go with GitHub Mobile for iOS > <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> > or Android > <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. > > -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/xrootd/xrootd/issues/1532#issuecomment-941050235 ######################################################################## Use REPLY-ALL to reply to list To unsubscribe from the XROOTD-DEV list, click the following link: https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-DEV&A=1