Thanks for replying, and let me explain a bit more... 1. Each "Pi" contains a control algorithm of real world. Each "property"/"variable" of discrete type keeps a history, either "each change" or "once in N minutes".
2. The history is kept in memory, and served from memory with REST API. 3. On reboots/resets/malfunction, the program loads all the history back in each "property". So, the primary purpose is simply to persist values to survive the Java process. And nothing else... However, I could imagine to offer longer history with a queryable DB under the hood, and free up a little bit of RAM (currently history is ~1500 properties, 350 entries in a Map<Long,Double>) Typically, these controllers are on 3G networks, alone, forgotten and have no datacenter to talk to. That is a feature. At the moment, I don't think that clustered use will show up, but I also don't want to rule it out. Maybe I should go with jdbm (a bit old and inactive) or mapdb (I had bad experience in the past), but thought to stick with Apache projects (I'm a Member) to eat my own dogfood. On Thu, May 9, 2019, 21:38 Jens Deppe <jde...@pivotal.io> wrote: > 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 >> >
