[GQI] Multi Select/Filter action performance impact

37 viewsGQI
2
0 Comments

Hi Community,

When join operator is used in GQI query and the amount of data is considerable big, is it important to think about the size of table (number of row) manipulated by the join action or to reduce the number of operator (select, filter)

Attached screenshot showing 2 implementations giving the same result:

  1. many select operator used to reduce the number of columns sent to 'join' operator which will decrease the outcome data size.
  2. All the data sent to 'join' operator without filtration to decrease the number of processing action

Please for your recommendation for such case.

Thank you in advance

Sebastiaan Dumoulein [SLC] [DevOps Enabler] Answered question 4 hours ago

1 Answer

2
12.48K 1 Comment

Hi Souhail,

Today it is indeed recommended to reduce the columns in the right side of your join (in your case the Get Elements query).

This is something that we can automatically optimize inside the GQI process as well. We'll follow-up on that and report back here once it's done.

Souhail Boucif [SLC] [DevOps Member] Posted new comment 4 hours ago
Souhail Boucif [SLC] [DevOps Member] commented

Hi Sebastien,

Well noted
Thanks for your feedback