You can determine the extent to which deduplication and compression reduce the amount of data that is sent over the network during transfer operations. You can obtain data transfer sizes by reading the View Client with Local Mode logs on the client computer.

During a check in or replication, the local desktop displays the amount of data that would be transferred to the remote desktop in the datacenter if no optimization took place. This amount does not reflect the actual data that is sent over the network. The same number appears whether or not deduplication and compression are enabled.

When both features are enabled, View Client starts by using deduplication to remove redundant data blocks from the data that will be transferred. Next, View Client either compresses the remaining data or determines that the data cannot be compressed.

To generate log entries that show deduplication and compression statistics, you must set the logs to Debug mode.

Location of View Client with Local Mode Logs shows the location of the View Client with Local Mode logs on the client computer.

Location of View Client with Local Mode Logs

Operating System

Path

Windows 8, Windows 7 and Windows Vista

C:\Users\user name\AppData\Local\VMware\VDM\Logs\

Windows XP

C:\Documents and Settings\user name\Local Settings\Application Data\VMware\VDM\Logs\

When a local desktop is checked in or replicated, View Transfer Server transfers the data that was generated on the local desktop since the last check out or replication. You can estimate the potential size of a data transfer if you know how long the desktop has been generating new data. The following sample log entry shows the amount of time, in minutes, since the last check out or replication:

2010-06-28 17:22:12,281 DEBUG <536> [wswc_localvm]
GetTotalCheckinSize: Total checkin size over 34 minutes:

The GetTotalCheckinSize log entries show the size of the transfer that is predicted before the transfer occurs. These numbers encompass all disks in the local desktop from which data is transferred.

The following sample entry shows the amount of data that will not be optimized by deduplication during a check-in operation. View predicts that this amount of data will be transferred.

2010-06-28 17:22:12,281 DEBUG <536> [wswc_localvm]
GetTotalCheckinSize: non-dedupe: 2 MB

In the following sample entries, the parent-dedupe entry shows the amount of data that will be optimized by deduplication on View Transfer Server. The self-dedupe entry shows the amount of deduplication on the client computer. Add the numbers in these entries to derive the total amount of data that will be optimized by deduplication.

2010-06-28 17:22:12,281 DEBUG <536> [wswc_localvm]
GetTotalCheckinSize: parent-dedupe: 871 MB
2010-06-28 17:22:12,281 DEBUG <536> [wswc_localvm]
GetTotalCheckinSize: self-dedupe: 0 MB

The Replication statistics log entries show the actual amounts of data that were sent over the network. Separate statistics are generated for each local desktop disk from which data is transferred.

In the following example, the parent-dedupe and self-dedupe entries show deduplication statistics on View Transfer Server and the client computer, respectively.

2010-06-28 17:24:53,046 DEBUG <BoraThread> [wswc_localvm]
Replication statistics:
2010-06-28 17:24:53,046 DEBUG <BoraThread> [wswc_localvm]
Parent dedup: 871.139 MB
2010-06-28 17:24:53,046 DEBUG <BoraThread> [wswc_localvm]
Self dedup: 0.000 MB

The following sample entry shows the amount of data that was compressed during a transfer operation:

2010-06-28 17:24:53,046 DEBUG <BoraThread> [wswc_localvm]
Compression: 0.000 MB compressed to 0.000 MB

The following sample entry shows the amount of data that was not compressed.

2010-06-28 17:24:53,046 DEBUG <BoraThread> [wswc_localvm] Raw
data: 2.198 MB

In this example, the local desktop displayed a message such as "Transferring 871MB". However, this amount of data was reduced by deduplication. Although the remaining data could not be compressed, only 2.198MB of data was transferred over the network.