Score reference

Dark Green

Olive Green

Yellow

Orange

The score for this category is based on the responses to user surveys.

The score for this category is based on the "crashiness" of the applications and the Operating System that the applications are installed on.

The score for this category is based on our patented technology that we call "Synthetic Micro-Transactions". We run these periodically on the device and perform different tests to measure the responsiveness of the device. This information cannot be obtained from any other solution.

A measure of end-users feelings about their experience based on user surveys.

Hardware utilization

System stability

Scores the frequency of operating system crashes (Blue Screens, or unexpected shutdowns). A lower score indicates crash activity, which is likely to be caused by a faulty or misconfigured device drive.

Scores the frequency of service failures (where a service fails to start or shutdown correctly). A lower score indicates problematic services which may need to be investigated.

Scores the frequency of software crashes. A lower score indicates a high rate of crashes. The Devices screen Logs tab can assist with investigation of software crashes.

Windows internals provides an indication of the timeliness of Windows System resource creation and availability

Derived from Operating System: Boot time

System disk performance

CPU performance

Sweet Spot Scoring Algorithm

Based on a bell curve. Define a range (minimum and maximum) and a sweet spot within that range.

Score is based on the distance from the nearest edge (minimum or maximum) to the sweet spot value.

Example: SweetSpot(0,100,15) given a value of 30 gives you a score of 83 which is a Good grading

Percentage Scoring Algorithm

Expect a value in the range of 0 - 100 and return that same value as the score. Dropping off any decimal points.

Example: A 9.6 value would give you a score of 9 which is a Very Poor grading

Inverting Algorithm

The result of this algorithm subtracts 100 from the value dropping any decimals.

Example: A 9.6 value would give you a score of 91 (100 - 9 = 91) which is a Very Good grading

Constant Scoring Algorithm

No matter the incoming value, return a constant score

Example: A value of 42 would give you a score of 42 which is a Poor grading

scores the I/O operations that were broken into multiple requests on the system disc. A lower score may indicate excessive disc fragmentation.

scores the average queue length for the system disc. A lower score indicates that this disc is not keeping up with the I/O backlog.

scores the average time taken for the system disc to perform a right. A lower score indicates that this disc is taking too long to service write requests.

scores the CPU Q length (backlog of processing work). A lower score means that the CPU is not keeping up with the workload.

scores the amount of time the CPU spent servicing interrupts. A lower score may indicate faulty or misconfigured hardware/ drivers.

scores the CPU load. A lower score indicates that the CPU is fully loaded, and additional processing power may be required.

Scores the amount of memory pages that had to be read from disc based storage. A lower score indicates this device is low on available physical memory.

Scores the percentage of the page file that is in use. A lower score indicates more high page file use, which may mean the device is low on available physical memory.

Scores the percentage of physical memory in use. A lower score indicates higher memory consumption, and therefore less available physical memory.

Score the time taken to allocate, zero and free a block of memory. A lower score indicates that the operating system is slow to server memory requests, which may affect application performance.

Scores the time taken to perform a basic loopback UDP send. A lower score may indicate problems with the operating system network stack.

Scores the network transmission backlog based on the length of the output packet queue.

Scores the signal quality of the wireless network connection on the device.

Scores the frequency of operating system crashes (Blue Screens, or unexpected shutdowns). A lower score indicates crash activity, which is likely to be caused by a faulty or misconfigured device driver.

Scores the frequency of service failures (where a service fails to start or shutdown correctly). A lower score indicates problematic services, which may need to be investigated.

Scores the frequency of software crashes. A lower score indicates a high rate of crashes. The Devices screen Logs tab can assist with investigation of software crashes.

Scores the frequency of software hangs (where an application becomes unresponsive). A lower score indicates a high rate of hangs.

Scores the time taken to create an empty, temporary file. A lower score indicates that the operating system may be underperforming in terms of basic file operations.

Scores the time taken to perform a random access disk operation on the system drive. A lower score indicates poor random disk access performance.

Scores the time taken to perform a sequential access disk operation on the system drive. A lower score indicates poor sequential disk access performance.

Scores the time taken to read from the HKLM Windows Registry hive. A lower score indicates poor registry read performance, which in turn may affect application performance.

Scores the time taken to write to the HKCU Windows Registry hive. A lower score indicates poor registry write performance, which in turn may affect application performance.

Scores the time taken to write to the HKLM Windows Registry hive. A lower score indicates poor registry write performance, which in turn may affect application performance.

Scores the time taken to create a new process. A lower score indicates that the operating system is taking a long time to create new processes.

Scores the time taken to create a new thread within a process. A lower score indicates that the operating system is taking a long time to create new threads.

Scores the time taken to acquire a basic operating system resource. A lower score indicates that applications may underperform because the operating system is slow to service resource requests.

Scores the time taken to load and unload a DLL in a process. A lower score indicates library loading is slow, which may affect the startup time of applications.

Scores the time taken for the device to boot to the logon prompt. A lower score indicates a long boot up duration, which may affect user satisfaction.

With the help of the toggle metrics scoring, an administrator can toggle a metric from contributing to its parent score and the final Experience score. To bring this change into effect, ensure that the weights of the metrics are updated appropriately and ignored metrics are added correctly in application settings.

Scores the time taken to generate an empty window. A lower score indicates poor Windows desktop performance, which may cause applications to appear unresponsive.

Scores the time taken to dispatch and confirm processing of a windows message. A lower score indicates poor message processing throughput, which may affect application responsiveness.