I'm not an expert by far, but when we had issues with our SP 2010 farm several years back (similar sounding issue, slow page loads), we did a RAP with Microsoft to pinpoint the major problems. After starting the RAP, they were able to help remedy some of the issues almost immediately, including the slow page loads. We are a Premier customer, so I have no idea if this is even an option for someone who is not (not sure if you are), but you might take a look.
The "obvious" stuff didn't seem to be the problem for us either (CPU, memory, etc). Just thinking back and looking at my notes, a few of the main takeaways that I remember were that we had to add another spindle to our virtual FE servers and split off the Blobcache, IIS logs, and indexing locations to the new drives. We also created multiple tempdbs for the SP SQL server (we have 8 now just for SP), and tempdbs have their own spindle set (physical server for us). Also, something about setting SQL autogrowth higher to 10% and checking the max memory is set appropriately for the server. I'm sure there's more, but maybe start searching on some of those items? -Bonnie From: [email protected] [mailto:[email protected]] On Behalf Of Damien Solodow Sent: Friday, March 18, 2016 10:51 AM To: [email protected] Subject: [NTSysADM] SharePoint assistance? Anyone know of (or happen to be) a good SharePoint engineer or one of the MVPs? We have a SharePoint 2013 farm that has some definite performance problems (front/home page takes several seconds to load), and are at our wits end. We even opened a support case with Microsoft which went exactly no-where; they gathered some logs and then just closed the case and refunded it without a word. DAMIEN SOLODOW Senior Systems Engineer 317.447.6033 (office) 317.447.6014 (fax) HARRISON COLLEGE 550 East Washington Street Indianapolis, IN 46204 www.harrison.edu<http://www.harrison.edu/>
