As you start your analysis in your Workspace, you may want to keep an eye on your Workspace's resources and storage to ensure that your scripts and queries do not cause your Workspace to fill up its storage, or use all of its running process capacity.

In this article, you will learn:

Prerequisites:

  • You can access a Workspace

Basic Workspace health tasks

To avoid an application in your Workspace from crashing, we recommend:

Monitoring a Windows Workspace

In a Windows Workspace, you can utilize the Task Manager to look at how much memory your Workspace has used up, and how much CPU and memory is available. By looking through the different tabs, you can see which applications are using up the most resources in your Workspace.

In the 'Processes' tab, there is a list of all applications which are open, and how much memory and processing the application is taking up in your Workspace. If a script or application is running slowly, check if the application is taking up a lot of memory. If it is, this can indicate several things:

  • Your scripts are not fully optimised, and need to be revised and improved to run faster and use less memory,
  • There are a lot of open applications using up memory, and reducing the available memory for your running applications,
  • Your application is dealing with a lot of heavy data work, and you may need a larger machine to handle the workload of your scripts and the data.

Freeing memory in Windows:

In your Windows machine, you can close your running applications, after saving your work, to reduce the amount of memory being used.

Monitoring a Linux Workspace

In a Linux Workspace, you are able to run a free command in the Command Prompt:

$ free -m 
total used free shared buffers cached
Mem: 7976 6459 1517 0 865 2248
-/+ buffers/cache: 3344 4631
Swap: 1951 0 1951

This information is displayed in MBs. The total os 7976 MB is the total amount of RAM installed on the system, that is 8GB in this example. The used column shows the amount of RAM that has been used by linux, in this case around 6.4 GB.

The catch over here is the cached and buffers column. The second line tells that 4.6 GB is free. This is the free memory in first line added with the buffers and cached amount of memory.

Linux has the habit of caching lots of things for faster performance, so that memory can be freed and used if needed.
The last line is the swap memory, which in this case is lying entirely free.

Freeing cached memory in Linux:

To free memory in your Linux machine, you can use the following commands:

1. Freeing Up the Page Cache

echo 1 > /proc/sys/vm/drop_caches

2. Freeing Up the Dentries and Inodes

echo 2 > /proc/sys/vm/drop_caches

3. Freeing Up the Page Cache, Dentries and Inodes

echo 3 > /proc/sys/vm/drop_caches

Related Articles:

Did this answer your question?