[
https://issues.apache.org/jira/browse/GEODE-5487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16576390#comment-16576390
]
Eugene Nedzvetsky commented on GEODE-5487:
------------------------------------------
We use most of regions in read-only mode. Typical our function modifies 1-10
records in one or two regions and reads a few thousand records from another
10-20 regions.
So we have a few TXEntrtyState#dirty=true records per transaction if
detectReadConflict = false.
In case of detectReadConflict=true it produces additional a few thousand
TXEntrtyState#dirty=true records which produces additional information in
TXLockRequest and additional network traffic between nodes.
It's a good point. First of all I'll create performance test.
GEODE-5557 duplicates GEODE-5486. GEODE-5486 has unit test with this issue.
> Choice of detect read conflict on transaction commit on a per-region basis.
> ---------------------------------------------------------------------------
>
> Key: GEODE-5487
> URL: https://issues.apache.org/jira/browse/GEODE-5487
> Project: Geode
> Issue Type: Improvement
> Components: docs, transactions
> Reporter: Eugene Nedzvetsky
> Priority: Major
> Labels: pull-request-available
> Time Spent: 1h
> Remaining Estimate: 0h
>
> Geode supports detect read conflict(-Dgemfire.detectReadConflicts=true) on
> transaction commit(see
> https://geode.apache.org/docs/guide/11/developing/transactions/transaction_semantics.html)
> This functionality can be enabled only on application level. It can
> dramatically decrease application performance.
> I propose to add ability to setup this property per region basis.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
