FSLogix CCD Driver – OS Test
The CCD (Cloud Cache Driver) specifically is part of FSLogix Cloud Cache, which helps users with profile data consistency across multiple locations (e.g., different datacenters or cloud regions). The CCD driver allows FSLogix profiles to be stored in multiple locations (local or cloud-based) and provides high availability for user profiles, even if one location becomes unavailable. Users can still access their profile data when network connections to the primary profile repository (cloud or on-premises) are unavailable. This is particularly useful in scenarios where users are working offline or from remote locations. FSLogix uses a virtual disk (VHD or VHDX) to store user profiles, and the CCD driver ensures that this disk is always available and synchronized across different caches, improving access speed and consistency.
Without sufficient disk space, profile containers can't be written to or read from the disk, resulting in users being unable to load their profiles. This can lead to slow logins, profile corruption, or session failures. For each user connecting to a FSLogix CCD Driver, this test reports whether the driver experiences a sudden bottlenecks during data read/write operation. In addition, the test helps administrators to manage user profiles more efficiently, with less risk of profile corruption and better handling of large user data.
Target of the test : A Citrix Desktop Group
Agent deploying the test : An internal/remote agent
Outputs of the test : One set of results for each combination of virtual machine:user on the target Citrix Desktop Group to be monitored.
Parameter | Description |
---|---|
Test Period |
How often should the test be executed. |
Host |
The nick name of the Citrix Desktop Group component for which this test is to be configured. |
Port |
Refers to the port at which the specified host listens to. By default, this is NULL. |
Inside View Using |
To obtain the 'inside view' of performance of the desktops - i.e., to measure the internal performance of the cloud-based citrix virtual desktops - this test uses a light-weight eG VM Agent software deployed on each of the desktops. Accordingly, this parameter is by default set to eG VM Agent. |
Report Powered OS |
If this flag is set to Yes (which is the default setting), then the 'inside view' tests will report measures for even those desktops that do not have any users logged in currently. Such desktops will be identified by their name and not by the username_on_desktopname. On the other hand, if this flag is set to No, then this test will not report measures for those desktops to which no users are logged in currently. |
Report By User |
This flag is set to Yes by default. The value of this flag cannot be changed. This implies that the cloud-based virtual desktops in environments will always be identified using the login name of the user. In other words, in cloud environments, this test will, by default, report measures for every username_on_desktopname. |
Is Cloud VMs |
Since this test runs for 'Citrix Desktop Group' component which is a cloud-hosted desktop group, this flag is set to Yes by default. |
Measurement |
Description |
Measurement Unit |
Interpretation |
---|---|---|---|
Usermode notification |
Indicates the number of usermode notifications received by this user. |
Number |
A usermode notification typically refers to a message or alert sent to the user of the desktop group running in usermode. These notifications are usually designed to alert the user without interrupting the workflow too much, and they are generated by the system running the desktop group |
Write data operations |
Indicates the number of data operations performed by this user. |
Number |
|
Usermode notify elapsed time |
Indicates the amount of time that has passed between a system event or notification being triggered in usermode and when the user actually receives or acknowledges that notification. |
Seconds |
A shorter elapsed time means the user is informed of important events or issues more promptly, which could lead to quicker resolution of issues or better awareness of the system’s status. |
Write data elapsed time |
Indicates the amount of time taken to complete a write operation. |
Seconds |
A high value of this measure could indicate a bottleneck. |
External data reads |
Indicates the number of external read transactions performed by this user. |
KB |
|
External data read rate |
Indicates the rate at which external read transactions performed by this user. |
KB/sec |
|
External reads |
Indicates the number of read transactions that were performed by this user. |
Number |
|
External read rate |
Indicates the rate at which write transactions were performed by this user. |
Operations/sec |
|
Local data reads |
Indicates the number of times data has been read after optimization. |
KB |
|
Local data read rate |
Indicates the number of times data has been written before optimization. |
KB/sec |
|
Local reads |
|
Number |
|
Local read rate |
|
Operations/sec |
|