[IGNITE-23199] Investigate GET scalability issues

• Type: Test
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 3.0
• Labels: ignite-3 important
• Ignite Flags: Docs Required, Release Notes Required
• Assignee: Vladislav Pyatkov
• Reporter: Alexey Scherbakov
• Created: 12/Sep/24 13:11
• Updated: 01/Oct/24 11:05
• Resolved: 01/Oct/24 11:05

Description

Current benchmark results show what GETs do not scale well, especially under high concurrency.

This should be investigated.

Issue Links

• relates to: IGNITE-23255 Fastest way to use Placement driver for RO transaction
• relates to: IGNITE-23257 Switch to partiton-operation thread to handle client messages
• relates to: IGNITE-23313 Avoid useing fulfilled hybrid time in SchemaVersions#schemaVersionAtNow
• relates to: IGNITE-23314 PartitionReplicaListener#ensureReplicaIsPrimary does not require to use hybrid timestamp
• relates to: IGNITE-23315 Use direct read transaction start time in case of the primary replica locally
• relates to: IGNITE-23316 Hybrid Clock#update can be optimized in case where return value is not needed
• relates to: IGNITE-23323 Do not increment hybrid clock timestamp in RO transaction