CPU Usage

As a User with System Administrator rights, checking the CPU usage of the Windows Server running SharePoint is helpful. It will identity if there are any overactive processes running and as a result providing reasons for performance degradation for other services e.g. RecordPoint. Some examples that can cause the the CPU usage to spike include:

IIS Worker Process (w3wp.exe)
SQL Server

To check the CPU Usage on the Server, open Task Manager and navigate to the Processes Tab.

IIS Worker Process (w3wp.exe)

It's important to keep in mind that it is normal for CPU usage to increase as a web application serves requests. However, if you consistently see CPU remain at a high level (in the area of 80% or greater) for prolonged periods, the performance of your application will suffer. For that reason, it's important to understand the cause of sustained high CPU so that it can be addressed and corrected if possible.

Go to Task Manager
Select the Processes tab
See the CPU usage shown as a percentage

Below is an example of a w3wp.exe with high usage.

To identify which application pool is associated with the w3wp.exe process:

Open Administrative: Command Prompt
Change the Directory to cd %windir%\System32\inetsrv
Enter the Command appcmd list wp
This will show the process identifier (PID) of the w3wp.exe process in quotes. You can match that PID with the PID available in Task Manager.

SQL Server

A contributing factor for seeing high CPU usage around SQL Server is from the Search Service Crawl running on the Server.

Go to Central Administration
Select Application Management
Select Search Service Application
Review the crawl settings for each content source i.e. schedules for incremental/continuous crawl

It is recommended that crawls are scheduled when there is low demand on the server resources.

Disk Utilisation (DU)

DU refers to the portion of computer storage that is currently in use.

To identify the disk utilisation, perform the following:

Select Settings
Select System
Select Storage
Select the drive you wish to see detail for
The storage usage, broken down by data type, will be displayed.

There are a couple of methods that can be used to reduce the DU.

Free up some disk space; and
Reduce the number of days that log files are stored on the Server.

To free up some disk space, perform the following:

Log in as a user who is a member of Farm Administrators group
Go to Server Manager
Go to Tools → Disk Cleanup to free up some Disk Space

To reduce the number of days that log files are stored on the Server, perform the following:

Go to Central Administration
Select Monitoring
Select Configure Diagnostic Logging
On the Diagnostic Logging page under Trace Log, modify the number of days to store log files box.

Logs

There are two log files to check on the server. They are:

SharePoint logs; and
Event Viewer logs.

To identify the level of logging recorded in SharePoint for the SharePoint and Event Viewer logs, perform the following:

Go to Central Administration
Select Monitoring
Select Configure Diagnostic Logging
Check if the logging levels are set to Verbose (Verbose logging usually results in Large Log files. Turn on Only when necessary).

SharePoint Logs

To identify how many logs are stored on the server, perform the following :

The default location of the SharePoint logs are stored here
(a) for 2016: C:/Program Files/Common Files/Microsoft Shared/Web Server Extension/16/Logs/ and
(b) for 2013: C:/Program Files/Common Files/Microsoft Shared/Web Server Extension/15/Logs/
Review the logs to identify any errors

Event Viewer logs

To view the event viewer logs, perform the following:

Go to Start
Go to Event Viewer
Select Window Logs
Select Application
Review Critical, Errors and Warnings

Services

Services in Central Administration

RecordPoint requires the below five services to be started, in order to function properly. They are:

Claims to Windows Token Service;
Managed Metadata Web Service;
Microsoft SharePoint Foundation Web Application;
Microsoft SharePoint Foundation Workflow Timer Service; and
SharePoint Server Search.

To verify the services are running, perform the following:

Go to Central Administration
Select System Settings
Select Manage Services on Server
Verify that the services are running on each web and application servers. These services should show status of Started. Here are couple of the Services mentioned from above list :

Services on the server

RecordPoint requires the following services to be running:

SharePoint Timer Service; and
Claims to Windows Token Service.