You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Vladislav Pyatkov (Jira)" <ji...@apache.org> on 2024/10/01 07:52:00 UTC
[jira] [Created] (IGNITE-23323) Do not increment hybrid clock timestamp in RO transaction
Vladislav Pyatkov created IGNITE-23323:
------------------------------------------
Summary: 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
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)