NP-View is a CPU and memory intensive application. At times, NP-View may appear to slow down, and the UI may become unresponsive. Here is a 3-step guide on how to improve performance:
Step 1: Ensure Correct Specifications
The most common issue being insufficient sizing of the desktop or server. Please validate the proper sizing of your system using the following links: Desktop requirements and Server requirements.
Symptoms due to insufficient sizing include:
- Low Disk Space - If the system runs out of available disk space, this will limit the ability of NP-View to process and store data. To resolve this issue, the user can perform a disk cleanup or add additional disk resources.
- Insufficient CPU - NP-View is a CPU intensive application, if the processing requested exceeds the available resources, the system usability will slow. In some cases, NP-View is put into a virtual environment where the allocated resources are not available on the hardware and the system slows. In some other cases, if connectors are running at the same time users are navigating the topology, the resources will be consumed by data processing and the system may appear slow.
- Insufficient RAM for the database - NP-View is a Memory intensive application, if the NP-View database exceeds the size of the available memory, the system usability may appear slow. NP-View utilizes a NoSQL in-memory database for performance. However, because the database is loaded into memory, if there is insufficient RAM on the system the database will become degraded or not run at all.
- Insufficient RAM for the system - If the end user has an older PC with 8 GB of RAM or less, the system may appear slow running on that PC.
- Excessive browser tabs - If the user has many browser tabs open which consume a lot of memory, the user interface may become slow or unresponsive. Close web browser tab to improve UI responsiveness.
Step 2: Limit the number of Devices per Workspace
Uploading many device configurations in a single workspace can lead to performance issues. For the Server application, a rule of thumb is to keep the number of devices in a single workspace to be less than 25. This limit should be reduced to 10 or even 5 in the case of large configuration files with thousands of rules, object groups, or end points. For the Desktop application, a single workspace should be limited to around 10 devices. In the case of large configuration files, we recommend a single device per workspace for the Desktop application.
If you encounter performance issue but the CPU, RAM, and disk space are sufficient:
- Divide your large workspaces into smaller workspaces,
- Reduce the frequency of configuration uploads through connectors from daily to weekly,
- Divide large views into smaller views, since large views with 1000+ endpoints may take a long time to save.
Step 3: Get Help from Technical Support
If the solution above do not work, please report your performance issue to technical support so it can be investigated and addressed. To contact the technical support team, please email npsupport@dragos.com.
