To recap, below you will find the previous articles:
- ThinIO facts and figures, Part 1: VDI and Ram caching.
- ThinIO facts and figures, Part 2: The Bootstorm chestnut.
Off topic note:
two years ago at an E2EVC event, the concept behind ThinIO was born with just a mad scientist idea amongst peers.
If you are lucky enough to be attending E2EVC this weekend, David and I will be there presenting ThinIO and maybe, just maybe there will be an announcement. Our session is on Saturday at 15:30 so pop by, you won’t be disappointed.
Back on topic:
So here’s a really interesting blog post. Remote Desktop Services (XenApp / XenDesktop hosted shared) or whatever you like to call it. RDS really presents a fun caching platform for us, as it allows us to deal with a much higher IO volume and achieve deeper savings.
We’ve really tested the heck out of this platform for how we perform on Microsoft RDS, Horizon View RDS integration and Citrix XenSplitPersonality with Machine Creation Services.
The figures we are sharing today are based on the following configuration and load test:
- Citrix XenDesktop 7.6
- Windows Server 2012 r2
- Citrix User Profile Manager.
- 16gb of Ram.
- 4 vCpu.
- LoginVSI 4.1 medium workload 1 hour test.
- 10 users.
- VMFS 5 volume.
Diving straight in, lets start by looking at the volume of savings across three cache types.