Skip to content
This repository has been archived by the owner on Jan 16, 2021. It is now read-only.

Capacity Limit of Reliable Collections in Stateful services #992

Closed
usamaazhar opened this issue Apr 19, 2018 · 3 comments
Closed

Capacity Limit of Reliable Collections in Stateful services #992

usamaazhar opened this issue Apr 19, 2018 · 3 comments
Assignees
Labels

Comments

@usamaazhar
Copy link

usamaazhar commented Apr 19, 2018

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

@olitomlinson
Copy link

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

https://stackoverflow.com/questions/36684805/azure-service-fabric-reliable-collections-and-memory

@masnider
Copy link
Member

@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).

@masnider
Copy link
Member

masnider commented Jun 7, 2018

@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!

@masnider masnider closed this as completed Jun 7, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

4 participants