Skip to content

[Storage][Perfstress] Downloads seems to be held in memory #16080

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
annatisch opened this issue Jan 11, 2021 · 1 comment
Closed

[Storage][Perfstress] Downloads seems to be held in memory #16080

annatisch opened this issue Jan 11, 2021 · 1 comment
Labels
Client This issue points to a problem in the data-plane of the library. pillar-performance The issue is related to performance, one of our core engineering pillars. Storage Storage Service (Queues, Blobs, Files)

Comments

@annatisch
Copy link
Member

When running large downloads (both FileShare and Blobs) over multiple threads - the process is being killed due to memory management. This does not happen using T1 SDKs. We should investigate memory management for the download APIs in comparison to T1 to confirm whether data is not being released as expected.

@annatisch annatisch added Storage Storage Service (Queues, Blobs, Files) pillar-performance The issue is related to performance, one of our core engineering pillars. labels Jan 11, 2021
@lmazuel lmazuel added the Client This issue points to a problem in the data-plane of the library. label Dec 17, 2021
Copy link

Hi @annatisch, we deeply appreciate your input into this project. Regrettably, this issue has remained inactive for over 2 years, leading us to the decision to close it. We've implemented this policy to maintain the relevance of our issue queue and facilitate easier navigation for new contributors. If you still believe this topic requires attention, please feel free to create a new issue, referencing this one. Thank you for your understanding and ongoing support.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Mar 15, 2024
@github-actions github-actions bot locked and limited conversation to collaborators Mar 15, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Client This issue points to a problem in the data-plane of the library. pillar-performance The issue is related to performance, one of our core engineering pillars. Storage Storage Service (Queues, Blobs, Files)
Projects
None yet
Development

No branches or pull requests

2 participants