You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 16, 2021. It is now read-only.
What is the size restriction of Reliable Collections in service fabric? Is it the size of the memory or the disk?
I read the answer here but just want to be sure on official forum url
The text was updated successfully, but these errors were encountered:
Memory (Ram) is the first limit you are likely to hit but you absolutely must read this response from @masnider to understand the complexity of defining the limit
@olitomlinson Thanks Oliver. @usamaazhar in that answer I didn't even talk about Garbage Collection/Garbage overhead and Serialization:) TLDR: Generally start with memory as your limit and you may be able to do more optimizations to reduce that footprint and to take advantage of disk, but those are not applicable in all situations. Please let us know if you have any further questions (or feel free to propose edits to that SO question).
@usamaazhar Hi there! We haven't heard back from you on this, so I hope my answer was sufficient. If you have further questions on this topic, please just let us know. For now I'm going to close down this issue. Thanks!
What is the size restriction of Reliable Collections in service fabric? Is it the size of the memory or the disk?
I read the answer here but just want to be sure on official forum
url
The text was updated successfully, but these errors were encountered: