SharePointSupport

You may have noticed that the hardware requirements for SharePoint 2013 Server are quite hefty. Many SharePoint 2013 performance issues have been attributed to lack of resources.  Although meeting the minimum performance specs is highly recommended, you can tweak SharePoint 2013 to work with less resources. The following tips are some that I have collected while looking for ways to improve SharePoint 2013 performance. Some of these will help SharePoint’s performance however, my experience has been that unless you have a server that meets the minimum SharePoint 2013 requirements, the Search function will still bring your SharePoint server to a crawl. The only way that I have been able to run SharePoint efficiently on a less than ideal server is to completely disable the search feature . If however, you want to try and tweak SharePoint before completely turning off the search service, be aware that performance results will vary depending on your server’s RAM and CPU speed

SharePoint performance is a recursive problem and preoccupation. As a Database Administrator, we have to deal with SharePoint when configuring SQL Server databases. In this article, I will propose a list of best practices in SQL Server settings aimed to reduce SharePoint performance issues. Autogrowth Do not keep the default value which is 1 MB. We can illustrate with a simple example why this is a bad idea. When a document of 5 MB is uploaded, it means there are 5 Autogrowth which are activated. In fact, there are 5 allocations of space which must slow your system. Moreover, your uploaded document will be fragmented across your different data files. This configuration will decrease your performance a second time. To avoid performance issues and reduce fragmented data files, you should set the autogrowth value to a fixed number of megabytes. My recommendation is 1024 MB for data files and 256 MB for log files. But keep in mind, this is a global recommendation. In f

I was about to give up on one of my labb SharePoint 2013 Environments because it was so extremely slow all the time. Warmup scripts, reloads, more memory, more CPU, stopping services, stopping search …nothing helped. I had a constant loadtime of all aspx pages of 6+ seconds, 6.10-6.20 something. Even when the page was just loaded and I pressed F5 to reload, it still took 6.10 seconds. This was an environment that gave you sensitive nerves… So, after looking for any solution or more like looking for the little issue that caused this all day, I gave up more or less. – CPU was at a maximum 40% on SQL, SharePoint cranked it up to 18%… – Memory consumtion was at 25% of the 12GB SharePoint had… – SQL was Lightning fast to all other SharePoint farms… – Network utilization showed about 100Kbps at the most… I scavenged the internet as usual and found nothing but the standard: add more memeory, add more CPU, stop services, stop search… None of that helped and I had tried it al

Why Performance Testing ? If you work on a team responsible for the delivery of SharePoint into your organization there's usually a mountain of tasks to complete before making it live. One of the most vital tasks is to make sure that SharePoint is "fast" enough to meet the requirements of your users. If you get performance problems after going live this can easily ruin all of your hard work and - even worse - your users will think SharePoint sucks! So, by the time you "go live" you should be confident of the following : You know the maximum load your service can take. You know your service can run for a pro-longed period of time. You know the point at which you may need to add more servers, so you can plan. When you do get to maximum load you need to know where the bottle necks in your service are, (e.g. SQL, Network, SP servers). If you don't know these metrics up front, then you are going to have to react as problems occur. If you have t

Very slow SharePoint, what can you do against it without upgrading your hardware : what you can do if your SharePoint is sometimes very slow. E.g.: on the first start of a Site Sometimes during the day a search query will take about a minute until you get results..... Just look on that article: http://support.microsoft.com/kb/2625048 it will improve your "feeled" performance (site response times) massive, if you're going to implement both solutions. Disabling CRL Check is just necessary if the SP Server does not have internet connectivity! -> that means proxy settings must be configured for the server itself http://technet.microsoft.com/de-de/library/bb430772(v=exchg.141).aspx , and your proxy must allow traffic from the server of course.