geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Swapnil Bawaskar (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (GEODE-354) For large values commit operation is noticeably slow when a commit conflict occurs
Date Wed, 23 Sep 2015 14:45:04 GMT

    [ https://issues.apache.org/jira/browse/GEODE-354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14904588#comment-14904588
] 

Swapnil Bawaskar commented on GEODE-354:
----------------------------------------

According to Darrel's feedback (https://reviews.apache.org/r/38628/#review100020), rather
than providing an option to turn off de-serialization, will make no de-serialization default,
and provide an option to de-serialize.

> For large values commit operation is noticeably slow when a commit conflict occurs
> ----------------------------------------------------------------------------------
>
>                 Key: GEODE-354
>                 URL: https://issues.apache.org/jira/browse/GEODE-354
>             Project: Geode
>          Issue Type: Bug
>          Components: transactions
>            Reporter: Swapnil Bawaskar
>            Assignee: Swapnil Bawaskar
>            Priority: Minor
>
> CommitConflictException message contains a readable version of the old and new entry.
In the case of a "commit" called from a GemFire client, this must be transmitted over the
network back to the client during the "commit" call.
> When using very large objects, on the order of a few megabytes, an option must be provided
to turn off the string conversion of values.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message