Anyone else seeing significantly decreased performance on the Loop piece in recent versions? What’s puzzling is that older flows are performing just fine, it’s newer flows (created since the PGLITE migration perhaps) that are choking during larger loops.
Looping over 1,000+ included items from an API call with minimal logic/steps takes 6 seconds on a legacy flow I’ve had for awhile.
Creating a new flow and looping over the same included items takes over 2 minutes.
At first the flow could not even make it through the array before timing out. Then I found this old thread and increased the AP_MAX_FLOW_RUN_LOG_SIZE_MB environment variable which allows the flow to run but performance is dreadful. CPU/RAM resources do not appear to be an issue.
Any help would be appreciated.
Self hosted, newest version.