What's New: Resource Governance for Business Central Online (2023 release wave 2)

Overview

The session explains the goal of resource governance: fair and optimal resource consumption for all Business Central Online customers on a shared multi-tenant service. It separates quotas, which are entitlements tied to licenses, from operational limits, which are fixed rules that apply equally to all users. It also describes the local and global consumption trackers.

It then walks through planned limit changes. Limits move from per environment to per user, with higher values for scheduled task concurrency and web service speed. A new execution time limit is announced for a future release. Limits are to be raised gradually during the preview period, and the speaker says details are subject to change.

Key points

• Quotas are entitlements or rights based on licenses. Limits are rules that apply equally to everyone. Entitlement quotas are announced and in the planning stage, estimated for the next two or three semesters.
• Entitlement quotas are planned to be tiered by license type, cumulative per environment and non-transferable between users. The aim is for 99% of customers to stay within quota, with add-on capacity or pay-as-you-go for excess consumption.
• Consumption is tracked by a local consumption tracker per user and environment in each cluster. A global consumption tracker aggregates across the tenant and applies customer-wide quotas.
• Scheduled task concurrency is planned to rise from 3 concurrent tasks per environment to 5 concurrent tasks per user, previewed early in the quarter.
• The web service speed limit is planned to change from 600 requests per environment per minute to 6,000 requests per user in a 5-minute sliding window, around November-December. Preview limits are subject to change.
• Web service concurrency keeps the same number, 100 concurrently handled requests (5 processed, 95 queued), but applies per user instead of per environment. The rollout is planned for the end of the quarter.
• An execution time limit for workloads is announced for a future release. Dynamic resource-based limits are applied internally and are not published. Throughput increases during the preview are gradual, not big bang.

Features

AL objects mentioned

As heard in the captions. A name that matches one object page by exact type and name links to it; the others stay as named.

• other “local consumption tracker” at 10:23
• other “global consumption tracker” at 10:43

Quotes

• 1:51 “is to offer optimal and fair resource consumption to all dynamics 365 business center online”
• 2:52 “we are planning to introduce this concept of quotas in the next uh uh few seme from now”
• 3:32 “quas are like entitlements or rights where customer and their user can claim or exercise those right while limits are laws or rules that”
• 6:28 “recently last year we started to track resource consumption so basically we want to track all type of workload and capacity unit”
• 13:04 “the ETA for this um uh new user base limit will be throughout this uh next quarter which is Art fourth quarter of calendar”
• 13:04 “we’re going to publish a clear user based limit that protect our service ensure fairness among users and Inspire elasticity and scalability the ETA”
• 13:44 “the user based limits uh are there to ensure fairness among users while the resource based limits are there to ensure fairness among customers”
• 15:20 “estimated happening in the next two or three semester from now uh the aim is like uh 99% of our customer will be able”
• 20:24 “we will actually uh upgrade the old concurrency limit for scheduled tasks from three concurrently running tasks per environment into five concurrently running tasks”
• 21:04 “changing the speed limit from the old for web service request from the old 600 um uh requests per environment per minute into actually”
• 22:05 “parallel web survey request 10 100 the same number 100 concurrently handle five uh process and 95 cute but per user”
• 23:26 “throughout um October November December we are actually making sure that this operational limit are continue to be monitored and fine-tuned pro to provide”
• 24:07 “we will do a gradual uh throughput increase let me just give you an illustration”

Disclaimers in the video

• 2:31 coming-later: we are planning to introduce this concept of quotas in the next uh uh few seme from now
• 13:04 preview: the ETA for this um uh new user base limit will be throughout this uh next quarter
• 13:24 preview: dynamic resource-based limit this is not published but this is something that we use underneath our service
• 15:20 coming-later: allow buying access consumption this should be um estimated happening in the next two or three semester from now
• 22:46 coming-later: in the future you can expect the introduction of the execution time limit
• 23:26 subject-to-change: expect expect it to change a lot sub it’s subject to change

Presenters (as heard): andaro.