• The dbo.tracelog table in the Foundation User Governance database may have exceeded 100 MB. If its size exceeds 100 MB, truncate the table. An oversized tracelog table can cause timeout issues on the site and impact various functionalities.

• Ensure that User Governance and Workflow Logging are disabled, as having them enabled can lead to performance issues.

• If you are using virtual machines (VMs), make sure to disable Dynamic Memory to optimize performance.

• Apply App Fabric CU 6 and make the necessary changes in the DistributedCacheService.exe.config file as described in this article: [Link: https://blogs.msdn.microsoft.com/calvarro/2014/03/20/points-to-consider-with-distributed-cache-on-sharepoint-2013-updated/]. These steps are crucial for improving performance.

• After applying any SharePoint Cumulative Updates (CU), run the configuration wizard on each server. Failure to do so may result in databases being placed in read-only mode, causing issues with Winshuttle.

• If users are experiencing issues with loading the number of items in folders, lists, or libraries on the Foundation site, check the list view threshold set in SharePoint.

• In case of performance degradation, performing an IISRESET can help improve performance.

• If you have multiple Winshuttle servers and a significant number of solutions and users, it is advisable to implement load balancing to distribute the workload efficiently.

• Regularly perform archiving to manage database size, as larger databases can negatively impact performance.

• If the size of the temp folder on the workflow server is causing performance issues, refer to the attached article for guidance.

• Verify that your system meets the recommended requirements outlined in our System Requirements guides. Remember to allocate additional resources (RAM and CPU) beyond Winshuttle’s specified requirements to account for the Windows OS, antivirus, and database needs. Insufficient resources can lead to system crashes or severe slowdowns.

• Check the paging files on your servers. If your system is paging, it indicates high memory consumption, which can slow down the server.

• Ensure that there are no DNS resolution delays by using the server IP instead of the name in the URL. Ping the Foundation server to measure the response time.

• Test the speed directly on the Foundation Server to eliminate any network-related issues.

• If using a virtual machine, reserve specific resources exclusively for that machine, avoiding resource sharing with other virtual machines.

• Make sure your PC is not connected to a VPN and is using Ethernet cabled connections instead of wireless connections.

• Exclude all Winshuttle folders and processes from antivirus scanning to prevent performance degradation.

• Reboot servers during scheduled downtime to ensure pending Microsoft updates are written correctly into the Windows registry.

• Utilize web debugging tools like Fiddler to analyze delays and troubleshoot performance issues. Refer to the link [https://www.telerik.com/fiddler] for more information and assistance.

• Slow logins or user delays can be caused by corrupted Windows credentials. Contact your IT department to recreate the user credentials.

• Temporarily bypass load balancers or web proxies to isolate any potential issues.

• Clearing the browser cache can help resolve performance issues.

• If the issue is specific to browsing tabs on the site, identify the particular solution causing the problem. Try redeploying the solution, as corrupted JS files or SharePoint lists might be the underlying cause. Refer to WIN-43120 for further reference.