login vsi company logo login vsi company logo 250x40
  • Home
  • Blog
  • The VDI Lifecycle: Six easy steps for the best VDI performance

The VDI Lifecycle: Six easy steps for the best VDI performance

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.

the vdi lifecycle login vsi and login pi together

Login VSI

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.

2: Compare

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.

3: Deploy

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.

Login PI

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.

4: Monitor

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.

5: Identify

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.

6: Report

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.

Conclusion

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.”)

Want more information about our products Login VSI and Login PI? Request a Login VSI demo or a Login PI demo today to get started.

About the author

Mark Plettenberg (@markplettenberg) is a product manager of Login VSI and has played a critical role in the development and growth of Login VSI. Ask Mark about motorcycle mechanics and breaking/repairing anything and everything that has a power plug.


Tags: Login VSI, Login PI, Monitoring, Load Testing

Popular Blogs

login-vsi-vdi-performance-summit

The VDI Performance Summit - Virtual Conference and Expo

Visit the VDI Performance Summit to gain knowledge and experience about performance and tuning VDI, improving End-User Experience and IT service. Join us at the ONLY virtual event 100% dedicated to VDI performance and tuning | May 2, 2019 This 1-day event offers key-notes presented by the best VDI performance experts in the world, technical and business oriented breakout sessions, the possibility to chat with experts directly to discuss your own situation, and a virtual exhibit hall featuring… Continue Reading

Scalability testing Parallels Remote Application Server with Login VSI

Recently I went to VMworld in Barcelona where Login VSI had a booth on the expo... While I can’t remember exactly how many conversations I had - there had been so many that I lost my voice on day one. What was new this year is that quite a few people asked if our software is compatible with the solutions from Parallels specifically their Remote Application Server (RAS) (Datasheet). Continue Reading
Login VSI Blog Article - Microsoft Windows 10 Default FTA Associations - Teaser Image

Windows 10 Default File Type Associations and Login VSI

When Login VSI 4.1 was released, the majority of desktops were running Windows 7 and life was easy. We’d set the default filetype for an application and it would simply work. The default and industry standard workloads in Login VSI include launching and using Adobe Reader as part of the virtual user simulation. Because Login VSI doesn’t always know which version of Adobe Reader is installed, or where it’s installed, the workload relies on the file type association (FTA) for .pdf documents to be… Continue Reading
Login VSI - Press Release - IGEL - Login VSI Partner to Optimize End User Computing Experience Image

[Press Release] IGEL Partners with Login VSI to Optimize the End User Computing Experience

Login PI enables organizations to better protect the performance and availability of their IGEL OS-powered virtual desktop environments San Francisco, USA, Feb. 6, 2019: IGEL, a world leader in software-defined endpoint optimization and control solutions for the secure enterprise, today announced that it is partnering with Login VSI, provider of software solutions to test and actively monitor the performance and availability of virtual desktop environments, including VDI and… Continue Reading
Login VSI - Blog - Login PI Blog Teaser Image - Windows Virtual Desktop: How To Monitor User Experience With Login PI

Windows Virtual Desktop – How to Monitor User Experience?

Microsoft has just announced the public preview of their new Windows Virtual Desktop (WVD) offering at Microsoft Ignite on Tour in Amsterdam today. For those of you who’ve not followed the rumors or the private beta, here’s the outline... Continue Reading
Investigating Online Application Performance with Login PI

Investigating Online Application Performance with Login PI

As many companies do, we use a CRM system. Recently, I have been getting complaints about our cloud CRM system, Microsoft Dynamics, being slow. I tried to investigate this by shadowing one of our users to see what was wrong. As expected, everything was fast. 15 minutes later, the same user reported slowness again. How could I investigate this without bothering the users? Continue Reading
Cookie Settings