High User Count/Low Power- What I mean by ‘low power’ is what we typically refer to as a “task user.” A task user is a desktop user that does not run any high IO applications. This is someone who is doing repetitive tasks amongst very few applications. The CPU and memory load that these applications produce is minimal, thus a high number of these types of users would not overload the CPU and memory allocated to the SnapVDI brick.
Low User Count/High Power- Typically referred to as a “Power User”, and the opposite of the first type of environment we described, a Low User Count/High Power type of environment means that the applications that are typically used are at a much higher IO level and are using up more of the CPU and memory resources. With more IO being utilized, the CPU and memory load is restricted to fewer users. Now this does not mean that these environments are not good fits for VDI, on the contrary, environments like this can save a lot of money by going to VDI since their high powered physical desktops are significantly more expensive than traditional desktops. These users sharing resources instead of working on the overprovisioned resources of a standard high performance desktop could create tremendous cost savings. The key here would be making sure that the CPU and memory allocated to the brick would be enough to cover the Power Users under a normal workload. A GPU may also be required here.
Any User Count/Medium Power- Commonly called “Knowledge User,” these are the most common types of users in most organizations. These users are your standard Microsoft Office, internet browsing, CRM using employees. As the title of this section indicates, these users occupy an amount of IO that is somewhere in the middle between task workers and power users. The great thing about using SnapVDI for a group of knowledge workers is that any number of users is a great fit. Since knowledge workers are most common in the workplace, SnapVDI bricks are named for how many knowledge users can fit in one brick, and even better, if an environment grows too large for one brick, more CPU and memory resources can be added on the fly to accommodate more knowledge users!
Bonus- Remote Users- If you work for an organization that has a number of remote locations, VDI is a wise topic to research. Continuously making special trips to remote locations to diagnose and fix desktop related issues gets old fast, especially if these remote locations are not incredibly convenient. Thus, the fewer hardware that organizations have to place at remote locations, the fewer opportunities there are for hardware failures at these remote locations.