[MCOL-5460] concurrent CTE operation excessive mutex Created: 2023-03-21  Updated: 2023-12-21

Status: Stalled
Project: MariaDB ColumnStore
Component/s: None
Affects Version/s: 23.02.1
Fix Version/s: 23.10

Type: Bug Priority: Critical
Reporter: alexey vorovich (Inactive) Assignee: Roman
Resolution: Unresolved Votes: 1
Labels: rm_perf

Attachments: PNG File CTE1-23_10_0.png     PNG File CTE1-3-patches.png     PNG File CTE2-23_10_0.png     PNG File CTE2-3-patches.png     PNG File CTE3-23_10_0.png     PNG File CTE3-3-patches.png     PNG File CTE3-3-patches_2.png     Zip Archive Columnstore-CTE-Test-Results.zip     PNG File screenshot-1.png     PNG File screenshot-2.png     PNG File screenshot-3.png     PNG File screenshot-4.png    
Issue Links:
PartOf
includes MCOL-5472 CPU wastes time in wait and sys b/c o... Closed
includes MCOL-5473 Mutex lock contention doing VSS looku... Stalled
includes MCOL-5474 Mutex lock contention doing block cac... Stalled
includes MCOL-5601 Config::makeConfig bottlenecks on a m... In Testing
Sprint: 2023-8, 2023-10, 2023-11, 2023-12

 Comments   
Comment by Roman [ 2023-03-22 ]

bbancroft CSV is OK.

Comment by alexey vorovich (Inactive) [ 2023-03-24 ]

leonid.fedorov we need to connect PR to this ticket

Comment by alexey vorovich (Inactive) [ 2023-04-03 ]

allen.herrera So did we recover the overall performance of concurrent queries enough ?

Comment by alexey vorovich (Inactive) [ 2023-04-03 ]

The key here is to estimate what regression in timing (or improvements) we have after the recent fixes as compared to 611

Comment by Roman [ 2023-04-03 ]

I need an access to the machines to see where is the bottleneck.

Comment by Leonid Fedorov [ 2023-04-04 ]

allen.herrera when you are referring 23.08.x release, that doesn't exist. Are you mentioning out last 23.02.2 package or 22.08.8? There is significant difference here

Comment by Roman [ 2023-11-01 ]

Added bunch of screens with sysbench results to compare 23.10.0 and the build that has 3 patches out of 4.
CTE3 didn't get any better that means there was no mutex contention in the first place.

Generated at Thu Feb 08 02:58:03 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.