Re: GeodeRedisAdapter improvments/feedback

Right.. Sent from Yahoo Mail on Android On Fri, Feb 17, 2017 at 8:05 AM, Wes Williams wrote: I'm not clear on the reference to "I like the idea of first class data structures like Lists and Sorted Sets." Is the suggestion here to extend Geode to not only support a

Re: GeodeRedisAdapter improvments/feedback

I'm not clear on the reference to "I like the idea of first class data structures like Lists and Sorted Sets." Is the suggestion here to extend Geode to not only support a distributed ConcurrentHashMap but also distributed ConcurrentList's and ConcurrentSortedSet's? *Wes Williams | Pivotal

Re: GeodeRedisAdapter improvments/feedback

I like the idea of first class data structures like Lists and Sorted Sets. I'm not sure which side of the fence I'm on in terms of very large objects and using Regions to represent them. Feels very heavy because of all the overhead of a Region entry in Geode (over 300 bytes per entry). I think

Re: GeodeRedisAdapter improvments/feedback

I think we as a community need to determine what value do we want to add with the Redis adapter. Redis already does a great job storing small data structures in memory and sharding them. We do a great job of making sure that these data structures are horizontally scalable; why would we want to

Re: GeodeRedisAdapter improvments/feedback

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

Re: GeodeRedisAdapter improvments/feedback

I think we are now straddling into the territory where any distributed storage gains would be negated by the memory we require to make the queries/lookup/operation fast. In addition to the added memory pressure, we still face network latency for every operation. On 2/15/17 15:12, Dan Smith

Re: GeodeRedisAdapter improvments/feedback

rg<mailto:u...@geode.apache.org><mailto:u...@geode.apache.org<mailto:u...@geode.apache.org>>" < u...@geode.apache.org<mailto:u...@geode.apache.org><mailto:u...@geode.apache.org<mailto:u...@geode.apache.org>>>; Hitesh Khamesra <hitesh...@yahoo.com<

Re: GeodeRedisAdapter improvments/feedback

On Wed, Feb 15, 2017 at 1:34 PM, Real Wes 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

Re: GeodeRedisAdapter improvments/feedback

e.apache.org<mailto:dev@geode.apache.org>>; > > " > u...@geode.apache.org<mailto:u...@geode.apache.org><mailto:u...@geode.apache.org<mailto:u...@geode.apache.org>>" > < > u...@geode.apache.org<mailto:u...@geode.apache.org><mailto:

Re: GeodeRedisAdapter improvments/feedback

ut if you want to > know > > > top 10 tweets which are trending then probably you want use > > > partition-region for "sorted-set". > > > > > > > > > From: Jason Huynh <jhu...@pivotal.io<mailto:jhu...@pivotal.io>> > > >

Re: GeodeRedisAdapter improvments/feedback

now > > top 10 tweets which are trending then probably you want use > > partition-region for "sorted-set". > > > > > > From: Jason Huynh <jhu...@pivotal.io<mailto:jhu...@pivotal.io>> > > To: dev@geode.apache.org<mailto:dev@geode.apache.org&g

Re: GeodeRedisAdapter improvments/feedback

t; <u...@geode.apache.org<mailto:u...@geode.apache.org>>; > Hitesh Khamesra <hitesh...@yahoo.com<mailto:hitesh...@yahoo.com>> > Sent: Tuesday, February 14, 2017 3:15 PM > Subject: Re: GeodeRedisAdapter improvments/feedback > > Hi Hitesh, > > Not sure abou

Re: GeodeRedisAdapter improvments/feedback

We should be careful here on a decision. If we start replicating fat lists/sets/hash maps synchronously every update, the Geode user will complain how slow the API is compared with Redis. Note: Redis replicates asynchronously. For fat collections we’re better off creating a region and

Re: GeodeRedisAdapter improvments/feedback

>>>The Redis adapter was designed so that we can scale all the Redis data structures horizontally. If you bring the data structures to region entry level, there is no reason for anyone to use our implementation over Redis. hmm, here we need to understand when we need to create partition-region for

Re: GeodeRedisAdapter improvments/feedback

,TreeSet> region; > > 6. Default config for geode-region (vote) > > I think the default setting should be partitioned with persistence and no > redundant copies. > > 7. It seems; redis knows type(list, hashes, string ,set ..) of each key... > > I suggested most operations

Fwd: GeodeRedisAdapter improvments/feedback

dis.io/commands/command> +1 for implementing the "COMMAND" -- Forwarded message -- From: Hitesh Khamesra <hitesh...@yahoo.com.invalid> Date: Tue, Feb 14, 2017 at 5:36 PM Subject: GeodeRedisAdapter improvments/feedback To: Geode <dev@geode.apache.org&

Re: GeodeRedisAdapter improvments/feedback

How's going on. What are you working these days. Sent from Yahoo Mail on Android On Tue, Feb 14, 2017 at 4:16 PM, William Markito Oliveira wrote: Definitely not by asking in the middle of on-going  discussion threads. Instructions: http://bfy.tw/A5ub :) Sent

Re: GeodeRedisAdapter improvments/feedback

l. But if you want to know > > top 10 tweets which are trending then probably you want use > > partition-region for "sorted-set". > > > > > > From: Jason Huynh <jhu...@pivotal.io> > > To: dev@geode.apache.org; "u...@geode.apache.org"

Re: GeodeRedisAdapter improvments/feedback

rending then probably you want use > partition-region for "sorted-set". > > > From: Jason Huynh <jhu...@pivotal.io> > To: dev@geode.apache.org; "u...@geode.apache.org" <u...@geode.apache.org>; > Hitesh Khamesra <hitesh...@yahoo.com> > Se

Re: GeodeRedisAdapter improvments/feedback

hoo.com> Sent: Tuesday, February 14, 2017 3:15 PM Subject: Re: GeodeRedisAdapter improvments/feedback Hi Hitesh, Not sure about everyone else, but I had a hard time reading this,  however I think I figured out what you were describing... the only part I still am unsure about is  Feedback

Re: GeodeRedisAdapter improvments/feedback

Definitely not by asking in the middle of on-going discussion threads. Instructions: http://bfy.tw/A5ub :) Sent from my iPhone > On Feb 14, 2017, at 6:38 PM, Michael Vos wrote: > > How do I unsubscribe from this email list? > > Thank you, > > Michael Vos > Strategic

Re: GeodeRedisAdapter improvments/feedback

The Redis adapter was designed so that we can scale all the Redis data structures horizontally. If you bring the data structures to region entry level, there is no reason for anyone to use our implementation over Redis. On Tue, Feb 14, 2017 at 3:15 PM Jason Huynh wrote: > Hi

Re: GeodeRedisAdapter improvments/feedback

In what format do you want the feedback Hitesh? For now I’ll just comment: 1. Redis Type String No comments except that a future Geode value-add would be to extend the Jedis client so that the K/V’s are not compressed. In this way OQL and CQ will work. The tradeoff of this is that the data

GeodeRedisAdapter improvments/feedback

Current GeodeRedisAdapter implementation is based on https://cwiki.apache.org/confluence/display/GEODE/Geode+Redis+Adapter+Proposal. We are looking for some feedback on Redis commands and their mapping to geode region. 1. Redis Type String   a. Usage Set k1 v1   b. Current implementation