I have been working with Sharepoint 2013 in our small office. However, i notice the sharepoint is very slow. Not always slow. Intermittent slow. When i first access the page it will take long for the page to appears. Then after that will be okay again. Then after a while when i click a link, the page will load very slow again and so on. Is sharepoint 2013 supposed to be like this?
Slowness of sharePoint due to many factors.
- you dont have enough hardware resources(CPU , RAM)
- You have heavy customization
- SQL Server may be
- Have Antivirus on the servers
- Network causing the slowness
- custom queris to database
- large List or libraries
How we can figured out and fixed it.
- I am big fan of Developer Dashbaord, this will give the break down of time during the page load. On which part it spend how much time.
- Config the perfmon on the SharePoint Server & SQL to Identify the bottle neck.
- Monitor the IIS logs, ULS logs and Event Logs.
You can avoid the issue.
- Confgure the different Cache avaiable in sharepoint i.e Output cache, object cache, and anonymous search results cache, Disk Based Blob cache
- take advantage of Bit Rate Throttling
- consider the upload file size limit as this may cause big hit on performance.
- exclude sharepoint directories for antivirus scan
- Distributed Cache
- Use the warm up script to avoid slowness of 1st time page load
Along with what others have said, there could be a secret culprit that I know I ran into when I had the same things happen to me. If you have any workflows associated with your site, check how many items are currently running. When I first started sharepoint, I assumed that if a workflow is waiting, it wouldn't take up too much resource allocation with the CPU, but every running workflow takes its toll. I had about 100 running workflows, and had to manually stop each one to fix the problem. If these workflows have loops that don't terminate, that would be even worse.
Again, just check how many workflows are running on your site, then check server CPU use and thread # to determine what is slowing everything down.
And, like your problem, when the server was shut off, and turned back on again, everything worked great. But after an hour or so, it would go back to being painfully slow.