Understand System and Resource Use in Umbrella Roaming Client

Introduction

This document describes the system and resource use for Cisco Umbrella Roaming Client.

Prerequisites

Requirements

There are no specific requirements for this document.

Components Used

The information in this document is based on Cisco Umbrella Roaming Client.

The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, ensure that you understand the potential impact of any command.

Overview

The Cisco Umbrella roaming client has a virtually nonexistent footprint on a computer in terms of system resources, both for Windows and Mac OS X. This is because the Umbrella roaming client does not cache DNS in any way, or expand in size or footprint over the course of time. DNS by design uses very little resources. This is also true of the Umbrella roaming client and the Umbrella service. The vast majority of computational power is held within Umbrella's cloud, not on the local machine.

The Umbrella roaming client, even if doing hundreds or thousands of DNS lookups per minute, does not fluctuate beyond what is described in this article. If you see the Umbrella roaming client's resource usage exceed the general outline of the parameters here and it is causing issues, please contact Cisco Umbrella Support.

Memory (RAM) & CPU (Processor)

The memory footprint of the Umbrella roaming client is consistently around 30 MB in macOS and Windows.

Windows

macOS

Storage (Hard Drive Space)

The storage footprint is about 7 MB of disk space for both Windows and Mac OS X, with the possibility of up to an additional 10 MB of logs being stored at any one time.