https://alguidelines.dev/bcbestpractices/performance/Recent content in Performance on AL GuidelinesHugo -- gohugo.ioen-ushttps://alguidelines.dev/bcbestpractices/performance/subscribercodeunits/Mon, 01 Jan 0001 00:00:00 +0000https://alguidelines.dev/bcbestpractices/performance/subscribercodeunits/<Created by waldo, Described by waldo> Description In general, subscribers have to be put in codeunits. There are a few performance considerations that you should keep in the back of your minds, when designing such a codeunit. Keep the codeunit as small as possible Work with a single instance codeunit only subscribe when necessary Avoid generic OnInsert/OnModify/OnDelete Let’s discuss all points Keep the codeunit as small as possible Every time a subscriber gets called, a new instance of the codeunit is being loaded in memory, which takes memory and processing power.