What is the recommendation for the maximum number of aggregate joins I can have in my service studio before it starts crashing, or having significant slowness/lagginess etc?
My laptop specs:
CPU: Intel Core i5-8365U @ 1.60 GHzRAM: 15.8 GBOS: Windows 22H2 (OS Build 19045.4894)
Under Edit > Preferences, I have tried the following:
1) Default checkbox for Auto-refresh data preview in Aggregates2) Uncheck the Auto-refresh data preview in Aggregates
I have 31 aggregates with 3 ONLY WITH joins and 28 WITH AND WITHOUT joins. The screen allows the end users to compare 8 different parameters to get a search result.
Each time I tried to change the joins criteria, there is a 20% chance my service studio will crash, and for the other 80% time I will experience sluggishness at the Service Studio. It gets so slow, that the mouse cannot move.
To fix the slowness, i have to split a single call to the DB into 3 different server action calls hence breaking down the 31 joins into 3 parts: 17 + 10 + 4.
I do not like this approach because I have to make 3 calls instead of 1 call. I took note of the Outsystems best practices to get the search result.
https://success.outsystems.com/documentation/best_practices/performance_and_monitoring/performance_top_10_rules/
https://success.outsystems.com/documentation/best_practices/performance_and_monitoring/performance_best_practices_queries/
It should not be an issue. But for outsystems we always use i7 computers.
Did you try on a coworker computer and have the same issue?
Thank you for your post Daniël.
Well... my coworkers either do not have such large amount of joins or they have i7 10th gen with 32 gb ram.
I could not find anything about the recommended specs for how many joins are ideals but in normal C# / PHP coding, i had tested the 40-50 joins in MSSQL Studio and it didn't crash.