Nimrod Becker
Nimrod Becker
I believe we were not able to bring all the fixes of caching into 5.6, @YiannisGkoufas would it be possible for you to use the 5.7 version ? we have...
yes. Would also require finer tuning for resources we allocate per each container (cpu, mem)
@jindong-ibm thanks for the info, it does scope what's needed and help us understand he exact request. It's not available now, but assessing the needed work, there isn't a lot...
We will keep the bug open of course :)
from the PR comment: "Notice that we still have a gap regarding the namespaceS3 aws sdk client configuration. Body sha256 calculation on v4 signature (in http requests)."
The BZ stated was closed as not a bug (not the tracker but the actual BZ it tracked...)
We can keep this issue until we have a task tracking this, basically, we wanted to go with something that eventually did not make it to openshift so we need...
No Jira ticket, this needs to be scheduled for a certain release
Can we verify if the 16ms average is on the endpoint side or the FS side? similar to what you did with the mv, can we run it and time...
It seems we would need to change the way we work with small files. We have an item on the roadmap to integrate with the SpectrumScale lib to increase performance...