Per my previous post, changing the Citrix HDX Thinwire Encoder on the fly, we can test the performance differences in the different encoder’s Citrix provides. I have done so by running through a demo of the Uniengine Heaven benchmark. The demo is exactly 4 minutes and 20 seconds long. I did a perfmon trace of the CPU %, total bytes sent in MBits/sec and the Thinwire Output in MBit/sec.
Time for some results!
|
|
Compatibility Mode (Encoder 0x0)
|
|
|
DeepCompressionV2Encoder (Encoder 0x1)
|
|
|
DeepCompressionEncoder (Encoder 0x2)
|
(Rollover the mouse on the next images to compare graphs)
|
|
CompatibilityMode vs DeepCompressionV2Encoder</p>
|
|
|
|
CompatibilityMode vs DeepCompressionEncoder</p>
|
|
|
DeepCompressionV2Encoder vs DeepCompressionEncoder</p>
|
The cumulative totals should help us get an understanding of the differences between the encoders:
</p> </col> </col> </col> </col>
|
|
CPU Total
|
ThinWire Total
|
Network Total (Mbytes)
|
|
DeepCompressionEncoder
|
5531.00
|
3693.28
|
540.51
|
|
DeepCompressionV2Encoder
|
5621.67
|
3684.75
|
539.74
|
|
CompatibilityMode
|
4197.54
|
3690.58
|
553.21
|
|
|
|
|
|
|
|
|
|
|
|
|
CPU Total
|
ThinWire Total
|
Network Total (Mbytes)
|
|
DeepCompressionEncoder
|
98.4%
|
100.0%
|
97.7%
|
|
DeepCompressionV2Encoder
|
100.0%
|
99.8%
|
97.6%
|
|
CompatibilityMode
|
74.7%
|
99.9%
|
100.0%
|
</tbody> </table> </div>
Interestingly, CompatibilityMode uses 25% less CPU then either DeepCompression Encoder. From what I see though the frames per second appears less for CompatibilityMode then the other two.
