[IGNITE-21458] Up to 25% performance drop in key-value operations (embedded node)

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Cannot Reproduce
• Component/s: persistence
• Labels: ignite-3 performance
• Assignee: Unassigned
• Reporter: Ivan Artiukhov
• Created: 06/Feb/24 08:38
• Updated: 05/Mar/24 11:44
• Resolved: 05/Mar/24 11:44

Description

AI3 rev. 
3cbec4fe80878765a50beeae09f6b352ebf718ec and 721b7ad6fc507c5f5e3b0129a68c5ed25ee14c06
 
Benchmark: https://github.com/gridgain/YCSB/blob/ycsb-2024.1/ignite3/src/main/java/site/ycsb/db/ignite3/IgniteClient.java 
The benchmark is started with useEmbedded=true, i.e. the Ignite 3 node and the benchmark is started within the same JVM.
The benchmark uses single key-value get and put. 

Steps:

Run the benchmark in load mode to put 300k entries using single key-value get() in 1 thread:

-db site.ycsb.db.ignite3.IgniteClient -load -P /opt/pubagent/poc/config/ycsb/workloads/workloadc -threads 1 -p recordcount=250000 -p warmupops=50000 -p dataintegrity=true -p measurementtype=timeseries -p status.interval=1 -p useEmbedded=true -p workDir=ignite3-work -p hosts=192.168.1.35 -s

Using the same persistence directory run the benchmark to get 300k entries using single key-value get():

-db site.ycsb.db.ignite3.IgniteClient -t -P /opt/pubagent/poc/config/ycsb/workloads/workloadc -threads 1 -p operationcount=250000 -p recordcount=250000 -p warmupops=50000 -p dataintegrity=true -p measurementtype=timeseries -p status.interval=1 -p useEmbedded=true -p workDir=ignite3-work -p hosts=192.168.1.35 -s

Results

Operation	721b7ad6fc507c5f5e3b0129a68c5ed25ee14c06	3cbec4fe80878765a50beeae09f6b352ebf718ec
put()
get()

See the drop the performance in 
3cbec4fe80878765a50beeae09f6b352ebf718ec.

Issue Links

• is related to: IGNITE-20373 Fix IO threading model