1. THINC: A Virtual and Remote Display Architecture for Desktop Computing Ricardo A. Baratto Network Computing Laboratory Columbia University

2. isolation...

3. Source: Internet Mapping Project (http://research.lumeta.com/ches/map/)... connectivity

4. dis-integration of the computer network storage clusters and grid computing

5. remote display display updates input

6. benefits

7. ubiquitous access

8. remote collaboration

9. online help

10. stateless client application processing and data secure server room thin clients

11. existing systems

12. what's wrong? problem: focused on office applications on LAN and reducing data transfer on low bandwidth links therefore: poor support for display intensive interactive applications poor support for higher latency WAN environments

13. THINC virtual and remote display architecture for desktop computing

14. contributions high performance remote display system [SOSP 05] first to natively support multimedia applications superior remote display support for mobile devices [WWW 06, SCC 06]

15. contributions II MobiDesk: desktop utility computing infrastructure [MobiCom 04, best student paper award] A 2 M: protect MobiDesk from DDoS attacks beyond remote display: desktop recording [SOSP 07]

16. THINC remote display simple display protocol  COPY, Solid Fill, Tile Fill, BITMAP, RAW focus on architecture of the system to improve performance  interception  translation  delivery

17. applications window system device driver framebuffer interception: traditional display pipeline

18. applications window system device driver framebuffer high-level requests interception  stateful client hurts mobility  app – window system synchronization

19. applications window system framebuffer device driver raw pixels high-level requests interception  lose semantics: expensive encoding

20. virtual display architecture

21. benefits

25. translation use and preserve semantic information for efficient translation

26. use semantic information when doing translation translation

27. use request semantics to generate update req: fill window W, color C application window system req: fill [x,y,w,h] color C THINC update: solid fill [x,y,w,h] color C

28. use semantic information when doing translation preserve semantic information throughout the system translation

29. why preserve semantics: offscreen rendering draw offscreen regions copy display

30. offscreen rendering (cont) ‏ offscreen region command log merge, clip, and discard commands as needed

31. delivery maximize interactive response of the system

32. delivery transmit updates as soon as possible merge, clip, and discard updates as needed... not all display content created equal

33. shortest remaining size first scheduler client buffer C1C1 C2C2 C3C3... CnCn real time...... queue 1 queue n cmd size

34. experimental results X/Linux prototype web browsing performance  comparison to existing systems  performance on wide area networks

35. web browsing performance... up to 4.8 times better performance

36. WAN web browsing performance

37. multimedia

38. existing systems

39. THINC multimedia native support for video playback bidirectional audio synchronized audio/video playback format independent and transparent to applications

40. video playback video player virtual device driver hw video acceleration interfaces YUV leverage client hardware scaling for free

41. audio applications OS virtual audio driver audio daemon audio data

42. experimental results

43. a/v playback quality... perfect playback and up to two orders of magnitude better

44. mobile devices becoming ubiquitous have network connectivity but limited environment and applications

45. pTHINC provide superior remote display support for mobile devices competitive alternative to limited mobile applications

46. ? server-resized updates

47. user interface zoom, scroll, rotate full screen by leveraging external controls

48. experimental results

49. PDA web browsing performance... up to 17x faster than other systems, and up to 8x faster than native

50. native vs pTHINC

51. btw

52. limitations need better compression  NX/SunRay/VNC, adaptive multimedia  too much bandwidth?  limited on mobile devices  flash video no support for new generation of high- end desktops and 3D applications

53. impact Technology licensed for commercial use VESA standard in progress

54. conclusions high performance remote display system able to outperform existing solutions first to provide full support for multimedia content, transparently to applications and independent of format superior remote display support for mobile devices

55. backup

56. Page-by-page comparison THINC faster on all pages except image-only Our approach works better than both low and high-level on non-image content

57. Microbenchmarks It's not each individual component, but the combination Not clear microbenchmark results can be extrapolated to overall performance But do have some results:  No offscreen: ~70% (all RAW) ‏  Only interception and redirection: ~225%

58. future work remote display standard (Net2Display) ‏ 3D indexing and searching improvements

59. list of publications MobiDesk: Mobile Virtual Desktop Computing [MobiCom 04] THINC: A Virtual Display Architecture for Thin-Client Computing [SOSP 05] Remotely Keyed Cryptographics: Secure Remote Display Access Using (Mostly) Untrusted Hardware [ICICS 05] pTHINC: A Thin-Client Architecture for Mobile Wireless Web [WWW 06] An Application Streaming Service for Mobile Handheld Devices [SCC 06] Net2Display: A Proposed VESA Standard for Remoting Displays and I/O Devices over Networks [ADEAC 06] DejaView: A Personal Virtual Computer Recorder [SOSP 07]

60. beyond remote display: desktop recording provide recording of all desktop output allow recording to be searched

61. text capture daemon index visual record client/ viewer applications virtual device driver visual output accessibility services text output desktop recording

62. recording runtime overhead

63. storage growth 32KB/s

64. wan a/v playback quality

65. mouth-to-ear latency overhead

66. PDA video playback quality

67. web browsing data transfer

68. A/V data transfer

69. PDA web browsing data transfer

70. PDA video data transfer

71. browse and search latency

72. playback speedup

73. web browsing performance... up to 4.8 times better performance

74. existing performance problem

75. implementation X/Linux and windows display server Linux audio driver (alsa) + daemon X/Linux windows, PDA, and Java clients X/Linux desktop recording  capture using ATK (Gnome) ‏  index using Postgres + Tsearch2

76. offscreen drawing draw offscreen regions copy display

77. offscreen region command queue command queues

78. client queue 1 2 3 3 2 1 copy onscreen

79. how? application s client hardware caps video

80. how we deliver updates display updates client buffer C1C1 C2C2 C3C3...CnCn

81. desktop virtualization decouple desktop from underlying video hardware encapsulate window and graphical state can move around:  carry in pocket  around hosting servers

82. MobiDesk

83. A 2 M: Access Assured Mobile Desktop Computing

84. old slides

85. contributions high performance remote display system [SOSP 05]  focus on system architecture to improve performance  outperforms existing systems first to natively support multimedia applications  transparent and format-independent wireless mobile device support [WWW 06, SCC 06]  server-side display scaling for improved display quality and performance  user interface tailored for constrained environment

86. contributions II MobiDesk: desktop utility computing infrastructure [MobiCom 04]  fully virtualized environment for hosting desktops  hosted sessions can be migrated for high availability A 2 M: protect MobiDesk from DDoS attacks  indirection-based network + remote display  exploit asymmetric traffic to minimize overhead beyond remote display: desktop recording [SOSP 07]  low overhead recording, and efficient access  novel use of accessibility services for indexing and searching

87. display protocol Inspired on Sun Ray protocol 2D Primitives copy solid and tile fill bitmap fill raw

88. demo

89. video leverage existing hardware acceleration interfaces YUV (luminance-chrominance) color space  format independence  client hardware acceleration (scaling for free) ‏

90. YUV Standard hardware interface Format independence Hardware acceleration (fullscreen for free!) ‏

91. isolation...

92. ... and a PC

93. system architecture as important as protocol and encoding

94. goals minimize latency simple and portable transparent operation

95. application requests translate command s deliver display updates THINC

96. basic static translation Draw API standard device driver command s THINC command s

97. high performance remote display LAN and WAN environments transparent operation in exisiting desktop systems full screen, full motion audio/video playback THINC

98. server-resized updates

99. system architecture

100. two key problems how do we translate from application commands to the display protocol? how and when do we send display updates?

101. but... performance problems  issues supporting display intensive interactive applications  issues coping with higher latency network environments lack of “features”  limited or no support for multimedia content  subpar support for mobile devices

102. system architecture is key interception translation delivery