[
https://issues.apache.org/jira/browse/IGNITE-23323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17901456#comment-17901456
]
Vladislav Pyatkov commented on IGNITE-23323:
--------------------------------------------
A method was described here and had been resolved in IGNITE-23314.
> Do not increment hybrid clock timestamp in RO transaction
> ---------------------------------------------------------
>
> Key: IGNITE-23323
> URL: https://issues.apache.org/jira/browse/IGNITE-23323
> Project: Ignite
> Issue Type: Improvement
> Reporter: Vladislav Pyatkov
> Priority: Major
> Labels: ignite-3
>
> h3. Motivation
> Hybrid clock is incremented in any time when we are getting a current
> timestamp. We can avoid increments, reduce latency in the case of RO
> transactions, and replace the cas operation with the only volatile read.
> {code}
> @Override
> public long nonUniqNow() {
> return latestTime;
> }
> @Override
> public HybridTimestamp nonUniqTimestampNow() {
> return hybridTimestamp(latestTime);
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
