You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/en/docs/refguide/modeling/community-best-practices-for-app-performance.md
+1-2Lines changed: 1 addition & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -61,8 +61,7 @@ Indexes is a topic with a long history of best practices from the database world
61
61
62
62
* Minimize the work in loops:
63
63
* Do commits and deletes after the loop in a list commit.
64
-
* If needed, create a list named `<Entity>_CommitList` before the loop and collect the items to be committed there.
65
-
Same for deletes with a `<Entity>_DeleteList`.
64
+
* If needed, create a list named `<Entity>_CommitList` (or `<Entity>_DeleteList`) before the loop and collect the items to be committed (or deleted) there.
66
65
* For retrieves in a loop, consider retrieving all the data before the loop, and do finds on that list inside the loop.
67
66
* If loops contain decisions, consider if the decision logic can be a query before the loop to minimize iterations.
68
67
* Prevent unnecessary retrieves if objects or lists can be passed as parameters.
0 commit comments