You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@geode.apache.org by "Chaudhary, Sushil (CONT)" <Su...@capitalone.com> on 2016/07/14 03:50:41 UTC

Copy-on-read | Geode

Does copy-on-read = true boost the Geode performance anyway?

Attribute       Description     Default
copy-on-read

Boolean indicating whether entry value retrieval methods return direct references to the entry value objects in the cache (false) or copies of the objects (true).
        False

Sushil Chaudhary
Email: sushil.chaudhary@capitalone.com
________________________________________________________

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.

Re: Copy-on-read | Geode

Posted by "Chaudhary, Sushil (CONT)" <Su...@capitalone.com>.
Thanks John.

Sushil Chaudhary
Email: sushil.chaudhary@capitalone.com

From: John Blum <jb...@pivotal.io>>
Reply-To: "user@geode.incubator.apache.org<ma...@geode.incubator.apache.org>" <us...@geode.incubator.apache.org>>
Date: Thursday, July 14, 2016 at 1:25 AM
To: "user@geode.incubator.apache.org<ma...@geode.incubator.apache.org>" <us...@geode.incubator.apache.org>>
Subject: Re: Copy-on-read | Geode

Yes, copy-on-read will have both a performance impact and resource impact (which invariably will affect performance).  Since it is "copying" data (on reads) it is increasing the memory pressure.

Typically, copy-on-read is only needed for Transactions (to prevent modification of the value in place).

On Wed, Jul 13, 2016 at 10:22 PM, Udo Kohlmeyer <uk...@pivotal.io>> wrote:

As Wayne said, copy-on-read will have a performance impact, as every "get" operation will create a copy and return that. Thereby pseudo-immutability.

--Udo

On 14/07/2016 2:46 PM, Wayne Lund wrote:
Its my understanding that copy-on-read will slow down the application, which is why the default is false.  If you're just using the reference like its pseudo-immutable than false is what you'd want to leave it.

Wayne Lund
Platform Architect
916.296.1893<tel:916.296.1893>
wlund@pivotal.io<ma...@pivotal.io>
www.pivotal.io<http://www.pivotal.io/>

[X]

On Jul 13, 2016, at 8:50 PM, Chaudhary, Sushil (CONT) <Su...@capitalone.com>> wrote:

Does copy-on-read = true boost the Geode performance anyway?

Attribute       Description     Default
copy-on-read

Boolean indicating whether entry value retrieval methods return direct references to the entry value objects in the cache (false) or copies of the objects (true).
        False

Sushil Chaudhary
Email: sushil.chaudhary@capitalone.com<ma...@capitalone.com>

________________________________
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.





--
-John
503-504-8657
john.blum10101 (skype)
________________________________________________________

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.

Re: Copy-on-read | Geode

Posted by John Blum <jb...@pivotal.io>.
Yes, copy-on-read will have both a performance impact and resource impact
(which invariably will affect performance).  Since it is "copying" data (on
reads) it is increasing the memory pressure.

Typically, copy-on-read is only needed for Transactions (to prevent
modification of the value in place).

On Wed, Jul 13, 2016 at 10:22 PM, Udo Kohlmeyer <uk...@pivotal.io>
wrote:

> As Wayne said, copy-on-read will have a performance impact, as every "get"
> operation will create a copy and return that. Thereby pseudo-immutability.
>
> --Udo
>
> On 14/07/2016 2:46 PM, Wayne Lund wrote:
>
> Its my understanding that copy-on-read will slow down the application,
> which is why the default is false.  If you’re just using the reference like
> its pseudo-immutable than false is what you’d want to leave it.
>
> *Wayne Lund*
> Platform Architect
> 916.296.1893
> wlund@pivotal.io <jo...@pivotal.io>
> www.pivotal.io
>
>
> On Jul 13, 2016, at 8:50 PM, Chaudhary, Sushil (CONT) <
> Sushil.Chaudhary@capitalone.com> wrote:
>
> Does copy-on-read = true boost the Geode performance anyway?
>
> Attribute Description Default
> copy-on-read
>
> Boolean indicating whether entry value retrieval methods return direct
> references to the entry value objects in the cache (false) or copies of the
> objects (true).
> False
>
> *Sushil Chaudhary*
> *Email*: sushil.chaudhary@capitalone.com
>
> ------------------------------
> 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.
>
>
>
>


-- 
-John
503-504-8657
john.blum10101 (skype)

Re: Copy-on-read | Geode

Posted by Udo Kohlmeyer <uk...@pivotal.io>.
As Wayne said, copy-on-read will have a performance impact, as every 
"get" operation will create a copy and return that. Thereby 
pseudo-immutability.

--Udo


On 14/07/2016 2:46 PM, Wayne Lund wrote:
> Its my understanding that copy-on-read will slow down the application, 
> which is why the default is false.  If you\u2019re just using the reference 
> like its pseudo-immutable than false is what you\u2019d want to leave it.
>
> *Wayne Lund*
> Platform Architect
> 916.296.1893
> wlund@pivotal.io <ma...@pivotal.io>
> www.pivotal.io <http://www.pivotal.io/>
>
>
>> On Jul 13, 2016, at 8:50 PM, Chaudhary, Sushil (CONT) 
>> <Sushil.Chaudhary@capitalone.com 
>> <ma...@capitalone.com>> wrote:
>>
>> Does copy-on-read = true boost the Geode performance anyway?
>>
>> Attribute 	Description 	Default
>> copy-on-read 	
>>
>> Boolean indicating whether entry value retrieval methods return 
>> direct references to the entry value objects in the cache (false) or 
>> copies of the objects (true).
>>
>> 	False
>>
>>
>> *Sushil Chaudhary*
>> *Email*: sushil.chaudhary@capitalone.com 
>> <ma...@capitalone.com>
>>
>> ------------------------------------------------------------------------
>> 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.
>


Re: Copy-on-read | Geode

Posted by Wayne Lund <wl...@pivotal.io>.
Its my understanding that copy-on-read will slow down the application, which is why the default is false.  If you’re just using the reference like its pseudo-immutable than false is what you’d want to leave it. 

Wayne Lund
Platform Architect
916.296.1893
wlund@pivotal.io <ma...@pivotal.io>
www.pivotal.io <http://www.pivotal.io/>


> On Jul 13, 2016, at 8:50 PM, Chaudhary, Sushil (CONT) <Su...@capitalone.com> wrote:
> 
> Does copy-on-read = true boost the Geode performance anyway?
> 
> Attribute	Description	Default
> copy-on-read	
> Boolean indicating whether entry value retrieval methods return direct references to the entry value objects in the cache (false) or copies of the objects (true).
> 
> False
> 
> Sushil Chaudhary
> Email: sushil.chaudhary@capitalone.com
> 
> 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.