Sharepoint 2013 very slow, improve performance

nothing from all that is from me and i'll post all the original links at the end.
* NOTE: most of these things are only optional if you dont use the search, and you must remember to undo everything when the time to use search has come.

* another note is that in reality you should have a fast HD, good connection, 4 CPUs, and if you heavily limit the noderunner.exe you can make it with 8GB.

* third note is that all that doent greatly improve the performance, but does help in a noteable amount, especially after doing Copy to Sharepoint Root, so its worth it but its not redemption.

1 - stop the search:
this one is a multi stage:
A - go to Central Admin -> Manage Services on Server and stop these:
        Search Host Controller Service     
        Search Query and Site Settings Service
        Distributed Cache       
B - Task Manager -> Services tab -> press the Services button and stop and disable the following:
        Sharepoint Search Host Controller
        Sharepoint Server Search 15   
     those sometimes comes back so u might be wanting to watch them.
C - go to "C:\Program Files\Microsoft Office Servers\15.0\Search\Runtime\1.0\noderunner.exe.config" and change to  <nodeRunnerSettings memoryLimitMegabytes="50" />

there are ways to just reduce the search, but here we completly disabled it.

another thing you can do is to open the Dashboard for further investigation
http://sps2013.blogspot.co.il/2012/07/developer-dashboard-in-sharepoint-2013.html

last this i still need to investigate is how to improve the SQL performance that seem to take affect too.
what i did that seems to help:
open the Management Studio -> right click on the server (the dad of the DB's) -> properties -> Memory tab -> i gave max query 2000MB
in the processors tab i checked the Boost SQL Server priority

links:
http://social.technet.microsoft.com/Forums/en-US/sharepointitpropreview/thread/16cebde9-da9e-43a2-9d6a-656693ab65c5/

http://social.technet.microsoft.com/Forums/en-US/sharepointgeneral/thread/e0d4b864-44c4-43ad-9a67-becdd11ff0cc

http://www.falconitservices.com/support/KB/Lists/Posts/Post.aspx?ID=109

http://www.lucacostante.com/item/13-sharepoint-2013-very-slow.html

http://blog.blksthl.com/2013/05/15/sharepoint-2013-page-loads-takes-a-very-long-time/

http://sharepoint410.wordpress.com/2012/10/22/sharepoint-2013-very-slow-in-loading-pages/

http://joelblogs.co.uk/2011/09/20/certificate-revocation-list-check-and-sharepoint-2010-without-an-internet-connection/


More on the coding part
1. make sure you dispose all SP objects, read this and its inner refrences
https://nhutcmos.wordpress.com/tag/spdisposecheck/

IIS - Warm/Wake up SP
IIS8 -  https://www.concentra.co.uk/blog/iis-application-initialisation-sharepoint-2013
others
https://gallery.technet.microsoft.com/office/SharePoint-2007-2010-or-d1884b4b
http://sharepointwarmup.codeplex.com/


Web Config:
<compilation batch='false'>

Slowness caused by lack of Internet Access:
1.      Slowness caused by lack of Internet Access:                                                               
Method 1
regedit: HKEY_USERS\\Software\Microsoft\Windows\CurrentVersion\WinTrust\Trust Providers\Software Publishing
http://ddkonline.blogspot.co.il/2010/05/fix-sharepoint-very-slow-to-start-after.html
Method 2
host file: 127.0.0.1 crl.microsoft.com
http://ddkonline.blogspot.co.il/2010/05/fix-sharepoint-very-slow-to-start-after.html
Method 3
<?xml version="1.0" encoding="utf-8"?>
<configuration>
      <runtime>
              <generatePublisherEvidence enabled="false"/>
      </runtime>
</configuration>
http://ddkonline.blogspot.co.il/2010/05/fix-sharepoint-very-slow-to-start-after.html
Method 4
Edit a group policy on the local server. Control Panel > Search for Policy > click Edit Group Policy > Computer Configuration >  Windows Settings > Security Settings > Public Key Policies > double click Certificate Path Validation Settings > click Tab Network Retrieval > click top check box to turn all check boxes on > set the 2 timeout values to 1. see Graphic  below.

Method 5
Install root cert
http://support.microsoft.com/kb/2625048
Others issues:
×          Disable/Reduce Search:
http://www.falconitservices.com/support/KB/Lists/Posts/Post.aspx?ID=109

×          Distributed Cache (6 sec slowness):
Make sure Distributed Cache is working correctly with domain account user:

http://technet.microsoft.com/en-us/library/jj219613.aspx   -> Change the service account








Comments

Post a Comment

Popular posts from this blog

OverTheWire[.com] Natas Walkthrough - JUST HINT, NO SPOILERS

game portal: http://overthewire.org/wargames/natas/ PASSWORDS for each level are stored in /etc/natas_webpass/natasX I made this walkthrough for people like me, i needed some help, but didnt want the spoiler, so here i will give you all the information needed to pass each level, yet not the solution. For levels needed custom web request i made a different post for powershell and javascript  with how-to's, since is a piece of learning for itself, and also for those of us that play at work and have only powershell at their hands. Although its not a complete spoiler there, its quite most of the solution so try yourself 1st. Natas The Natas game is from basic to advances web hacking. Every few levels is about whole new exploitation (with some harder ones doing comeback later), so a lot of learning. If you're new, you're the reason i am writing so much even for the 1st level, just please google EVERY topic you see, since in the following levels i assume you know the
Read more

SOLVED The item could not be indexed successfully because the item failed in the indexing subsystem

if you got an error like this The item could not be indexed successfully because the item failed in the indexing subsystem. ( The item could not be indexed successfully because the item failed in the indexing subsystem.; Failed to recover content group; Aborting insert of item in Link Database because it was not inserted to the Search Index.; ; SearchID = 04081656-B51B-4DCD-96D4-6DB2D2CEEEE7 ) as well as these: The item could not be indexed successfully because the item failed in the indexing subsystem. ( The item could not be indexed successfully because the item failed in the indexing subsystem.; Caught exception when preparing generation GID[7]: (Previous generation (last=GID[6], curr=GID[7]) is still active. Cannot open GID[7]); Aborting insert of item in Link Database because it was not inserted to the Search Index.; ; SearchID = 92EB0180-C086-4853-BED8-F4878D9748AD ) the solution for me was to clear configuration cache (PS)  and then restart SP Search Services. THX to m
Read more

Asp.Net Ending Response options, Response.End() vs CompleteRequest()

this blog is for any1 who get the ThreadAbortException when caling Response.End(), and then tried the other options such as HttpContext.Current.ApplicationInstance.CompleteRequest() and found out that there was no replacement. i'll start with the bottom line: if you want to stop right now your response and send it as is you dont have any other option other than Response.End(), period and it's the right thing to throw that EX in that case. the answer is its because there is the "HTTP pipeline" and the "Asp.Net pipeline", and CompleteRequest() cuts the HTTP pipeline but not the Asp.Net one so everything that is from handlers forwars (including all page events) continues but your part, the asp one, stays in your hands so that no information will be lost, so ur suppose to manage your code currectly, since information lost is really a bad thing, although in most cases we use Response.End() we know what we are losing and we want it. see this short article ab
Read more