Microsoft/alguidelines
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

deploy: b8be6ed4b3

Browse source
This commit is contained in:
JeremyVyska 2022-02-15 21:05:07 +00:00
parent e4f08bf9a7
commit 7274dae657
178 changed files with 4703 additions and 3605 deletions
Download patch file Download diff file Expand all files Collapse all files

4
bcbestpractices/performance/index.xml Normal file
View file

@ -0,0 +1,4 @@
<?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>&amp;lt;Created by waldo, Described by waldo&amp;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&amp;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>