We have done the same sizing activity recently for the move from XenApp shared server desktops to Win10 VDI. That said, memory is not going to be your limiting factor in your systems anyway, it will be CPU. 6 GB would be more than enough, even 4 GB would probably be doable. So an example: let's say you go with 2x 24-core Intel Scalable Gold 6252, at 2.1 GHz, that would mean you could get 96 users on that system.įor that amount of users, I would look into AMD EPYC 7002 though, more cores, higher clock speed and cheaper than Intel Scalable.įor the memory, 8 GB also seems a bit much for that type of user, especially if you would be looking to optimise the image. Don't count the hyper-threads, they only add about a 20% performance increase, and are best used as a buffer for spikes. ![]() Even if you give the desktops 2 vCPUs, pessimistically, they'll probably never use more than 1 GHz most of the time, so depending on the clock-speed of the CPU's you choose, you divide the clock speed by 1, then multiply by the amount of physical cores. I wouldn't do 1:1 for the CPUs, it's not needed for that type of user. Would of course look to optimize the image (no appx,cortana,defender,search etc)Īny thoughts regards memory/vCPU sizing really appreciated ! (for storage looking into that separately) - just looking at a 1:1 sizing perspective the specs look huge so any real world experience here would be great The workload would be pretty standard office 2016 / skype (at present but will be replaced with teams later this year). Going 1:1 and doing the sums on that figure indicates I would need 12TB of RAM and 3000vCPU ports which seems pretty astronomical - my query is have other folks got experience Want to err on the side of caution and go with the "heavy" recommendation of At present users are running in a hosted shared environment(2008 r2 published desktops) and as the hardware they are running is out of maintenance soon need to buy new kit.įrom a sizing perspective have been pondering how much memory / VCPU we'll need. In that case, the desktop module would assume the shape and style currently selected for their icon equivalents.In the midst of looking to purchase kit for a 1500 user windows 10 VDI environment. So, instead of two virtual themes based on style, I could simply add '' or something like that to the top of the Themes context menu. ![]() On the other hand doing it like this could create even more confusion because this 'basic version' of desktop modules could then have a different style from their icon equivalent. If the user then selected one of those virtual themes, the desktop module would then assume the shape and style of its icon equivalent. and for the clock module, and for the net/ram/cpu meter modules, etc.) as 'virtual' themes right at the top of that menu. This opens a menu displaying all themes that include skins for that desktop module, and allows you to, for instance, apply a specific theme only for that module.įirst I thought that I could add the two basic styles (e.g. Now, perhaps there is something I can do to work around this: when you right click a desktop module, one of the options in the context menu is 'Theme'. ![]() Otherwise, if a user selected the digital style for the clock icon module, from then on the desktop clock module would never again change shape regardless of what theme the user switched to, simply because no theme has a 'digital clock' skin for the clock desktop module. As such, they might take 'hints' from the currently selected style for that particular module, but that is as far as it goes. ![]() Icon modules have two styles/looks, desktop modules, however, only have one look. They do share some properties with their 'icon' equivalents, but their shape is usually different (unless the theme author did not include a skin for that module, in which case the desktop module would use the same shape as its icon equivalent). Thanks for the thumbs up, and for the screenshot.Īs you read and I explained elsewhere, desktop modules are free form and defined by the current skin/theme.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |