Enabling mouse shadow can in many circumstances force XenDesktop to switch from efficient client cursor rendering to latency prone server-rendered cursors. One of the newer costly graphical features that has appeared in desktops is mouse shadow. If the tail is chopped off then the mouse is server rendered, a client-rendered mouse being overlaid would retain its tail. In XenApp, it is very easy to recognise a server-rendered cursor by dragging the mouse to the edge of an application window. when they are scrolling or moving a window rapidly.Ĭlient-rendered cursors involve the instruction to redraw the mouse being done on the client and simply overlaid upon the “background” desktop. It can also result in a lot of redrawing of transient intermediate frames that are unnecessary, intermittent information that a user doesn’t need e.g.
a complex CAD model where the application is recalculating the part) this can become a bottleneck. This can generate high-bandwidth and if the desktop is very complex (e.g. Every time the user moves their mouse, that message is sent to the server, so the desktop can be redrawn and then the new desktop is sent back to the user. Server-rendered cursors are expensive for virtualised desktops. This means there are two potential places a cursor can be added on top of the desktop, 1) on the server or 2) on the client device.
Vmware player mac os x jittery mouse windows#
Until I joined HDX and started researching them, I had no idea how complicated and troublesome a little arrow could be! Citrix XenDesktop and XenApp both involve constructing a desktop on a server and then remoting the pixels of the desktop to an end-client device that end-client device could be a Windows workstation, a Linux thin client, an iPad or a smartphone. Citrix App Delivery and Security Service.