The geode client is also "bucket-aware", so the writes will go directly to the primary from the geode client once it's warmed up and discovered the PR metadata.
Are you using multiple threads? What are your conserve-sockets settings? With the defaults on pool size and conserve-sockets, the geode client might actually use more sockets and have less contention on the sender. -Dan On Tue, May 10, 2016 at 1:25 PM, Darrel Schneider <[email protected]> wrote: > Did you do the puts in both cases using putAll? > > On Tue, May 10, 2016 at 1:00 PM, Real Wes Williams <[email protected] > > wrote: > >> I am looking at a client that is writing 1 million puts in ~5 >> milliseconds across 2 nodes. >> >> To boost performance, I wrote a peer with local-max-memory=0 to write the >> same 1M puts. After some time to let the buckets warm up, the puts took ~29 >> millis. >> >> In GemFire XD the peer driver was more performant than the client driver >> and so I expected the Geode peer to write faster than a client because it >> is “bucket-aware”. >> >> What am I missing in that I expect a peer to write faster than a client >> but the reality is reversed? >> >> Thanks, >> Wes Williams > > >
