4 lines
No EOL
1.4 KiB
XML
4 lines
No EOL
1.4 KiB
XML
<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Performance on AL Guidelines</title><link>https://alguidelines.dev/bcbestpractices/performance/</link><description>Recent content in Performance on AL Guidelines</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><atom:link href="https://alguidelines.dev/bcbestpractices/performance/index.xml" rel="self" type="application/rss+xml"/><item><title>Subscriber Codeunits</title><link>https://alguidelines.dev/bcbestpractices/performance/subscribercodeunits/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://alguidelines.dev/bcbestpractices/performance/subscribercodeunits/</guid><description>&lt;Created by waldo, Described by waldo&gt;
|
|
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&rsquo;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.</description></item></channel></rss> |