Jump to content

Recommended Posts

Posted

This might be one for @jamesbmarshall as I'm not sure how many places are using SharePoint on Office 365 at present?

 

We're currently developing an Intranet based on SharePoint Online within Office 365. Thus far we have noticed it can be a bit sluggish so trying to tweak it as much as possible before going live. One thing I wonder that may help is increasing the Server Resource Quota allocated to the site (currently on the default of 300).

 

There's not much documentation on exactly how this works - is it used as a ratio within your tenancy e.g. if there's two sites with the same quota does that split available resources 50:50 or is it a case of the more resources you throw at it the faster it gets?

 

We've got 10,000+ users provisioned so the number of resources available is also pretty large, just wondering if there's a guide to how much you need and how much it impacts on performance? Should we just assign all available resources to the site now then carve it up as we create more site collections or is there an argument for keeping the number at a reasonable limit?

 

We do have custom sandboxed code deployed on the front page (live calendar, events etc.) which I believe is what the resources relate to, which might affect the choices above.

 

Any info much appreciated.

  • Thanks 1
Posted
Good question, we're also just about to deploy our SharePoint intranet site and noticed it still being rather sluggish even though I've upped the resources to 100,000 (a third of the available).
Posted

The server resource quota is the number of resource 'points' sandbox solutions can consume before they are turned off for the day. Upping it means that resource intensive sandbox solutions will continue to run for longer, but it doesn't increase the performance of the site.

 

To increase the performance, it would be better to convert the sandbox solutions to apps which then run off the server allowing the page to load and render quicker.

  • Thanks 1
Posted
Unfortunately SharePoint feels sluggish all round the site, not just our home page where the customisations live. MS need a few more hamsters in their server farm it seems...

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...