The article discusses the benchmark between setting "Filtering attributes" and "Filtering attributes = All" when registering plugin steps in Dataverse. The author creates two identical tables and plugins with similar logic to calculate totals based on certain attributes. They then perform a benchmark using BenchmarkDotNet to compare the performance of different plugin steps. The results show that setting filtering attributes to the attributes that trigger the plugin improves performance, but the difference is not significant. The article also mentions that running multiple plugin steps with filtering attributes performs better than single plugin steps without filtering attributes. However, the difference becomes more substantial when introducing "Post Async Update" steps.
Login now to access my digest by 365.Training