Anthony,
Thanks for the reply.

I have region defined as either as PARTITION or REPLICATED.  Can I use 
scope="distributed-no-ack"
With the region type = PARTITION_HEAP_LRU.


create region --name=regionB --type=PARTITION_HEAP_LRU --redundant-copies=1 
--total-num-buckets=5003


My aim is to get the best performance for IMDB, I am fine to have async copy of 
buckets across node to get better performance. Also, we have 500Millions 
key/values to put into IMDB. What do you think should be best bucket size to 
get best performance.  I tried increasing it to high number (prime number) but 
does not see improvement in gets/puts rate.

We are evaluating Geode, against other IMDB like hazel cast and Ignite and have 
go choose one to get the enterprise version.  Best performance is key criteria. 
Please let me know.

Sushil Chaudhary
Email: [email protected]<mailto:[email protected]>

From: Anthony Baker <[email protected]<mailto:[email protected]>>
Reply-To: 
<[email protected]<mailto:[email protected]>>
Date: Thursday, July 14, 2016 at 12:57 PM
To: <[email protected]<mailto:[email protected]>>
Subject: Re: Sync copy of buckets across Replication | Geode


Here are some links to Pivotal-hosted documentation (note that this is an 
interim hosting solution until the docs are donated to the geode project):

http://geode.docs.pivotal.io/docs/developing/distributed_regions/choosing_level_of_dist.html
http://geode.docs.pivotal.io/docs/developing/partitioned_regions/how_partitioning_works.html

Anthony

On Jul 14, 2016, at 6:21 AM, Chaudhary, Sushil (CONT) 
<[email protected]<mailto:[email protected]>> wrote:

Anthony,
Thanks for the reply. Do you have any docs/link on the same?

Sushil Chaudhary
Email: [email protected]<mailto:[email protected]>

From: Anthony Baker <[email protected]<mailto:[email protected]>>
Reply-To: 
<[email protected]<mailto:[email protected]>>
Date: Thursday, July 14, 2016 at 12:32 AM
To: <[email protected]<mailto:[email protected]>>
Subject: Re: Sync copy of buckets across Replication | Geode

Geode does synchronous replication of updates by default.  Changes are 
replicated prior to sending the client response.
________________________________
The information contained in this e-mail is confidential and/or proprietary to 
Capital One and/or its affiliates and may only be used solely in performance of 
work or services for Capital One. The information transmitted herewith is 
intended only for use by the individual or entity to which it is addressed. If 
the reader of this message is not the intended recipient, you are hereby 
notified that any review, retransmission, dissemination, distribution, copying 
or other use of, or taking of any action in reliance upon this information is 
strictly prohibited. If you have received this communication in error, please 
contact the sender and delete the material from your computer.

________________________________________________________

The information contained in this e-mail is confidential and/or proprietary to 
Capital One and/or its affiliates and may only be used solely in performance of 
work or services for Capital One. The information transmitted herewith is 
intended only for use by the individual or entity to which it is addressed. If 
the reader of this message is not the intended recipient, you are hereby 
notified that any review, retransmission, dissemination, distribution, copying 
or other use of, or taking of any action in reliance upon this information is 
strictly prohibited. If you have received this communication in error, please 
contact the sender and delete the material from your computer.

Reply via email to