As we experience successes with Project Online, more and more users find reasons to use it. In some heavy usage scenarios, the issue of performance may exist. Despite Project Online being Software as a Service (SaSS), tenants are not 100% clear from administrative responsibility of maintaining a responsive system. It is something Microsoft and each tenant mutually must address. Though 85% or so percent of actions are on Microsoft to administer, there are a set of decisions/actions each tenant must make before and after the system implementation. I have broken actions into a table for a quick reference use and identify when decision should be made.
To help make this shared responsibility abundantly clear, Microsoft provides tenant administrators with an interface to manage storage and server resource quotas, see below:
The storage quota is straight forward, but the server resource quota can be confusing. It represents an allocation of processing weight and the available resources for sandboxed custom code. Available resources are derived from a formula that includes number of users. Per this TechNet answer, it is or was a formula like this: (#seats×200)+300 (https://social.technet.microsoft.com/Forums/office/en-US/737311d1-3057-4ee6-b26e-79a86bf43c14/what-is-server-resource-quota?forum=sharepointgeneral) .
The tenant admin, therefore, should allocate a higher value to applications that are more demanding. The default value is 300 and can be set to zero to disable sandboxed code. However, changing these limits will not do much in my experience. In scenarios where multiple PM’s publish large schedules simultaneously or a lot of users submit timesheets with single entry mode enabled, or other general heavy usage, there still may be a hit on overall performance regardless of optimal resourcing of site collection.
To tweak performance, see table below of my recommendations from most impact to least.
Decisions/Actions to Extend Project Online Limits
For more comprehensive information on limits and performance tuning, all tenant administrators should be aware of these two articles:
Project Online: software boundaries and limits, https://support.office.com/en-us/article/Project-Online-software-boundaries-and-limits-5a09dbce-1e68-4a7b-b099-d5f1b21ba489
Tune Project Online performance, https://support.office.com/en-us/article/Tune-Project-Online-performance-12ba0ebd-c616-42e5-b9b6-cad570e8409c
Bottom line, Microsoft and each tenant are responsible for the performance of Project Online. There are some effective configurations that can be made per instance of Project Online. However, in the bigger picture of extending limits of
Project Online is general practical use. There is nothing practical anyone can do apart from actions in the table above if a horde of PM’s publishes projects with thousands of tasks. Microsoft has your tenancy wrapped in a controlled processing container. If there are a lot of updates there is more processing work. A successful deployment of Project Online will address this and so should getting business practice to prevent all PM’s from publishing at the same time.