SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Does code that is deployed through a Sandboxed solution perform just a well as code deployed through a Farm solution?

Does the overhead that comes with interprocess communication (since Sandboxed code runs in SPUserCodeV4.exe) have any effect on the performance of custom code?

share|improve this question

I asked that question at the SharePoint Conference and they said there shouldn't be any performance difference. I agree with you though, I would think that unpackaging the wsp, opening a new process, and returning the result would means slower page loads on whatever is using that functionality.

share|improve this answer

There should be almost no difference. In any case the extra time required for interprocess communication is very small compared with getting data from the database.

There are two main reasons to use a sandboxed solution:

  • You plan to deploy it to the cloud (SharePoint Online Services)
  • To improve managability and security

There are many situtations where the requirements of a system do not allow you to use a Sandboxed solution.

share|improve this answer

Just turn on Developer Dashboard.

My experiment: Page with farm web-part - Execution Time 38.95 ms
Page with empty sandboxed web-part - Execution Time 384.12 ms

This only one sandboxed web-part that do noting...

share|improve this answer
Correct, I have experienced a slow down too. This is down to how sandboxing works - creating a copy of the page object, running the sandbox with that, then merging back to the parent page object. – Mauro Nov 17 '14 at 11:42

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.