The VDI Lifecycle: Six easy steps for the best VDI performance
It’s the Circle of Life. With this song stuck in my head since the mid-1990s, now is the time to do something useful with it. I present to you the circle of VDI, also known as the VDI lifecycle.
The VDI lifecycle includes every stage of a VDI environment from development to production. By moving through these steps as a continuous process for every software or hardware change in your VDI environment, you will be able to locate performance issues upfront without receiving complaints from your end users.
Update May 25, 2016:
My colleague Dennis Damen introduced an updated version of the VDI Lifecycle of only four steps to deliver the best VDI user experience.
To measure is to know. To know the impact of a change before deployment to real users, you need to test. Login VSI can help you be proactive by employing simulated or virtual users with realistic user behavior to show you how many users your environment can support before performance starts to degrade.
1: Test & Validate
When implementing a change in your environment, the first step is to Test and Validate the performance impact of this change. Run the test with Login VSI and use the performance analyzer to check the results.
Next, you can compare the performance of this change to earlier test results or different (VDI) solutions to make sure that you make the right decision. Is the performance better, the same or worse? And how does change A compare to change B. For example how does Microsoft Office 2010 compare to Office 2013, don’t be surprised if you see a 20% decrease in the amount of users you can get on a server with this one.
Step 3 is to decide whether or not you should implement this update in production. Maybe you should wait for the next update or change the configuration and go back to Step 1 to test and validate again. But if all is good you can deploy with confidence. Or as Mufasa says, “I’m only brave when I have to be.”
Is everything looking good? Then it’s time to deploy this change to live production.
After deploying an update in production, you want to make sure that everything keeps working consistently. That’s where Login PI comes in. Login PI gives you performance insights that help you get and stay ahead of trouble tickets.
Login PI monitors your environment by adding a virtual user to your environment. This virtual user constantly reports on performance of applications. Since he is using the same applications as your real-life users, you will get a lot of insights in the end user experience.
Login PI helps to identify performance issues before your end user notices them, so you can take action before users are impacted. As the Login PI user is virtual, it can identify issues 24/7 even when there are no real users on the system. For example, Login PI can alert you on an issue that occurred at 4:00 am that you would have normally found out about at 8:30 am when the first users try to log on.
The reports generated by Login PI enable you to compare the performance of your production environment to historical data to notice any changes. For example: are the response times around 9:00 am always slower or is something else going on? This is also a great way to validate if you or your DaaS or cloud provider has reached the requirements set in the Service Level Agreement (SLA).
After identifying an issue, always make sure to test and validate the solution with Login VSI before deployment to make sure that everything performs great before bringing it to production.
The VDI lifecycle is a continuous process that will help you to deliver predictable performance, higher availability and a more consistent end user experience. We truly believe that this will make both your end users and yourself very happy.
If you’ve ever experienced the pain of downtime or unhappy end users, Login VSI and Login PI working together can help your IT organization completely avoid those performance problems. (And yet another Lion King quote begs to be expressed: “Ah yes, the past can hurt. But the way I see it, you can either run from it or learn from it.”)