Hi Niclas, A 256MB heap might work but is not optimal. We'd probably need more info on your actual use case / topology to answer definitively, but here are some general thoughts:
- Could your Pis just be Geode clients that feed the data to a larger cluster? - If storing data locally in regions, you could use OVERFLOW regions that overflow their *values* to disk and just keep the keys in memory. - Depending on the size of the data you are storing, it might be OK. Is your data compressable? --Jens On Wed, May 8, 2019 at 10:18 PM Niclas Hedhman <nic...@hedhman.org> wrote: > Hi, > I am considering putting Geode in an app that runs in a rather small > memory device (think Raspberry Pi). Performance is not the reason, but that > it may be reconfigured to be replicated to a "real" computer if needed, so > only a few thousand updates per hour or so. > > When running embedded, can I set the max memory Geode will use? And would > it work with something like 50MB, 100 at the most, for Geode (a 256MB JVM > heap)? > > Cheers > Niclas >
