sharepoint 2013 extremly slow

Question

I've been utilizing SharePoint 2013 on-premise, and it had been functioning smoothly until recently when its performance significantly declined. Within the setup, I've configured workflows for task generation and forwarding. Incremental crawling is scheduled daily at 7 PM and typically completes within 5-10 minutes, while full crawling occurs every 4 months. Whenever a task is created or forwarded to a user, an email alert is triggered. Additionally, when an announcement is uploaded to SharePoint, email alerts are dispatched to approximately 70 recipients. The server hosts four sites, equipped with 32 GB of RAM and 2 TB of storage. Currently, the accumulated data consists of around 800 GB of documents/files, totaling approximately 80,000 documents. However, in the past couple of days, the performance has drastically deteriorated. Upon analyzing the log files, I've observed recurring warnings.

1. 05/20/2024 15:28:08.99 w3wp.exe (0x10B4) 0x1D44 SharePoint Foundation Configuration 8059 Warning Alternate access mappings have not been configured. Users or services are accessing the site http://myprod with the URL http://'192.168.0.205'. This may cause incorrect links to be stored or returned to users. If this is expected, add the URL http://192.168.0.205 as an AAM response URL. For more information, see: http://go.microsoft.com/fwlink/?LinkId=114854"/>
2. 05/20/2024 14:58:08.57 w3wp.exe (0x10B4) 0x1CF4 SharePoint Foundation Monitoring b4ly Medium Leaving Monitored Scope (Render Ribbon.). Execution Time=10.34904 cb792aa1-7d7e-009f-404f-4ff82defd1f7
3. 05/20/2024 14:58:08.60 w3wp.exe (0x10B4) 0x1CA4 SharePoint Foundation Request Management advu2 High [Forced due to logging gap, cached @ 05/20/2024 14:58:08.10, Original Level: Verbose] Size of data: '{0}' bytes cb792aa1-7d7e-009f-404f-4ff82defd1f7

Answer 1

Hi @Muhammad Akram,

There are a few possible reasons for the performance decline in SharePoint 2013 on-premises. One possible reason is that the server is running out of memory. The context suggests that peak memory usage for the server should be around 9.2-9.4 GB, but the user's server only has 32 GB of RAM. Additionally, the log files indicate that there have been warnings related to memory, such as "something went wrong while displaying this page. error code out of memory". To address this issue, the user may need to consider upgrading the server's memory.

Another possible reason for the performance decline is that there may be issues with the server's configuration, such as the alternate access mappings not being configured correctly. The log files indicate that there have been warnings related to alternate access mappings. To address this issue, the user may need to review and update the server's configuration.

Finally, it is possible that the accumulated data of around 800 GB of documents/files, totaling approximately 80,000 documents, is causing the performance decline. The context suggests that scaling out (increasing the number of computers that host SharePoint Server 2013) is an option to consider if more throughput is needed.

---

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.