Deltas would help. If the regions are persistent, the whole new value does get written to disk though.
I suppose a third option would be to store all collections in the same region, but store each element of the collection as a separate entry. For example for HSET rkey rfield rvalue would create an entry with a geode key of (rkey, rfield) in a REDIS_MAPS region. We could index the based on rkey. That might make operations on the entire collection more expensive though; those operations would all require using OQL queries. -Dan On Wed, Feb 15, 2017 at 2:35 PM, Galen M O'Sullivan <gosulli...@pivotal.io> wrote: > On Wed, Feb 15, 2017 at 1:34 PM, Real Wes <thereal...@outlook.com> wrote: > > Does delta propagation make worrying about frequently updated fat > collections moot? > > As long as we don't have collections on the order of the available RAM on a > single server (in which case we'd want to distribute it across multiple > servers), and pending testing, I think it does. Good idea, I didn't even > know we could do this. >
