I read a good article on LinkedIn by our colleague Mark Warren. It was about Pre-Allocation for avoiding model saves. Model saves may have impact on performance.
Please see the LinkedIn post: https://www.linkedin.com/posts/mark-warren-45649ab_reducing-saves-in-data-hubs-activity-679639748978...
The led me to the idea:
I as a model builder want to be able to configure Pre-Allocation for a List in the Configuration tab of the List because this will be the intuitive place to manage, will prevent workarounds to get the Pre-Allocation done and will be a more visible feature to manage the performance for specific user stories
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.