Knowledge Base

Dell Data Protection Endpoint Recovery Resource (CPU) Usage

This article describes Dell Data Protection | Endpoint Recovery Resource Usage.

Affected Products:

Dell Data Protection | Endpoint Recovery

At rest

Unlike most services, DDP | ER was very carefully architected so that when it isn’t backing up (or restoring) it uses literally zero CPU. It has a number of threads – but they are all paused waiting for something (such as the Scheduled backup timer to tick). So, when nothing is happening the service is invisible. We did this in anticipation of our eventual port to mobile battery-operated devices and for laptops.

During execution

When DDP | ER is running a backup it uses no more than 1 Core internally. It’s likely that some of the system calls we make use more than 1 core but those should be a minority of the operations. I’m doing a System State backup on my tablet and I just looked at it and it is peaking at 25% CPU usage (on a dual core I3). This, unfortunately, has the side effect that we’re not the fastest backup in the race. We architected the product to be unobtrusive, not a jackrabbit.

The User Interface

Now, the user interface is another matter. It is a C# application that was not written to be particularly resource-efficient. Worse yet, when it’s running it communicates (a lot) with the service and so both the GUI and the service CPU usage goes up noticeably when you run the GUI.

Implications of turning on Background

When you enable the Background system setting, DDP | ER runs Job threads as background tasks. This means that the task will run at normal speed unless the CPU cores are required for something higher priority. In our testing this has minimal effect unless you are severely loading your computer.

For any questions/concerns, please call Dell Data Protection ProSupport at: 877.459.7304 Ext. 4310039. For support outside the US, reference ProSupport’s International Contact numbers list. You can also join us on our Dell Security Community Forum.

Article ID: SLN300011

Last Date Modified: 02/28/2017 11:30 AM

Rate this article

Easy to understand
Was this article helpful?
Yes No
Send us feedback
Comments cannot contain these special characters: <>()\
Sorry, our feedback system is currently down. Please try again later.

Thank you for your feedback.