none
Site Collection Resource Quota - Recommended Practice

    Question

  • I have been searching for recommendations on the value to use for setting the Resource Quota for a site collection in an Office 365 tenant for SharePoint. I have found several articles on how to change the setting, and how it is calculated (in theory), but nothing on what the recommended setting should be for a typical team site or publishing site that is not using Sandbox solutions.

    Use Case 1 - Typical team site, no customizations, less than 50 users

    Use Case 2 - Publishing site, client side code (JS, HTML, CSS) customizations, up to 5,000 users 

    Use Case 3 - Corporate Portal, rich content, custom pages, search driven content, again, client side code, around 30,000 users

    These are all hypothetical, but with only client side code, and OOB capabilities, do we need to set a Resource Quota? The default sites for search center, portal, etc. have a quota of zero. Does zero mean unlimited resources, implying we should not use that for any site that is not provided OOB? If the tenant overall resources hit the total value, does that bring the whole tenant down? What is the impact of setting the value to zero? Can the total of the resource quotas exceed the total available, as long as the tenant does not exceed the total in operation?

    A nice article explaining when and how to determine Resource Quota values, other than trial and error, would be helpful.

    Thursday, April 7, 2016 10:11 PM

Answers

  • I believe, but have had conflicting information, that the quota relates to sandboxed code limits. I was told that it was used to compute the relative priority of a site collection so you'd get higher prioritization for a site with more resources allocated to it but that seemed impractical/improbable.

    If your tenant has allocated all of your resources then you can't assign more. That's all. It is not possible to over provision resources (as you can with storage).

    If a site runs out of resources (assuming the sandboxed limits) then the site will stop working in part or completely.

    It would be nice to get a definitive write up but that's true of so many O365 aspects that it's unlikely MS are going to provide one here.

    Friday, April 8, 2016 8:26 AM
  • If I understand correctly resource quotas are used to limit the risk that sand-boxed custom code can have on your site collection quota i.e. CPU and Memory. 

    So regardless of your use cases, if you are not  using any custom code i.e. Sandbox solutions then you can leave it to whatever is the default. 

    I am not 100% sure about this but I have ran few tests myself for 100 users and 500 users but it did not make any difference with the resource quota. What you need to worry about is your storage quota depending on how much storage you would want to use. 

    If you want to read really good article on storage quota then Mark have done a great job on that. A must read article on storage quota.

    Managing Resources in SharePoint Online (Office365) Site Collections
    Tuesday, April 19, 2016 10:42 PM
    Moderator

All replies

  • I believe, but have had conflicting information, that the quota relates to sandboxed code limits. I was told that it was used to compute the relative priority of a site collection so you'd get higher prioritization for a site with more resources allocated to it but that seemed impractical/improbable.

    If your tenant has allocated all of your resources then you can't assign more. That's all. It is not possible to over provision resources (as you can with storage).

    If a site runs out of resources (assuming the sandboxed limits) then the site will stop working in part or completely.

    It would be nice to get a definitive write up but that's true of so many O365 aspects that it's unlikely MS are going to provide one here.

    Friday, April 8, 2016 8:26 AM
  • If I understand correctly resource quotas are used to limit the risk that sand-boxed custom code can have on your site collection quota i.e. CPU and Memory. 

    So regardless of your use cases, if you are not  using any custom code i.e. Sandbox solutions then you can leave it to whatever is the default. 

    I am not 100% sure about this but I have ran few tests myself for 100 users and 500 users but it did not make any difference with the resource quota. What you need to worry about is your storage quota depending on how much storage you would want to use. 

    If you want to read really good article on storage quota then Mark have done a great job on that. A must read article on storage quota.

    Managing Resources in SharePoint Online (Office365) Site Collections
    Tuesday, April 19, 2016 10:42 PM
    Moderator