As they were the only pair in the shop, I tried them on and did the new shoe walk up and down the store and told my folks they fit perfectly. To this day, I have feet like a Hobbit. I cannot stress to you how much size matters. Sorry folks! One of the tasks, that as an architect, you will be required to do from time to time is to assess a solution based on a set of requirements. Sometimes, you will not have the luxury of true benchmarking or testing, but we do have tools to utilise for such exercises as Login VSI and Login PI.
I will move on to the advantage of such tools in later articles. Sometimes you will be forced to do some theoretical sizing, and this will be based on a set of requirements and best practice and a little bit of simple arithmetic. What do you really need to be aware of when sizing a Citrix solution from the ground up?
That is quite significant, and if you do not take this in to account when sizing a solution, you will be preparing to fail. Although you might be right in your math when it comes to sizing, you may have missed out on some fundamental points I listed above on what to factor in. If you do not take this in to account when carrying out your theoretical sizing, you might fall short. Taking the information we have above, we can work out the following for a Citrix Application workload:.
Most of the time your resource constraint will be the CPU. You have decided that you want no more than 30 users per Citrix Application server.
You are scaling out not up. There are some recommendations out there that range from 1 to 2 and having software like WEM can help in this area. Contention Ratio for CPU in this example is Read your VDI Handbook! We want 30 users divided by total number of users required Total users to work this sum out.
We round up remember so we get Citrix Application Hosts that we require. We know that we cannot have 5. Rounding up at this point would provide 6 hosts which we do not have the capacity for. We figured out that we require 5 Citrix App hosts per Citrix Hypervisor host which we divide by total Citrix Hypervisor hosts. We round up as we cannot have Are we confident at this stage this is a true figure? Remember the requirements and the performance hits?
We also need to look at the DR requirements and take this in to consideration plus growth. The next set of figures may change slightly depending on when you apply the figures but, in this scenario, I will apply the growth figure last.
Also when using web sites the web sites are slow if video is present. Initially, there were 4 physical servers. All servers were R2, and were 64 bit. Newest server was a 2 proc, 64MB ram citrix XenDesktop server. Second oldest was a single proc, 32MB ram citrix XenDesktop server. The last two were AD servers with 8MB ram. Mix of mirrors and raid 5 arrays. I upgraded 2 and 3 year old computer to 96MB ram and both have 2 procs. I installed VMWare 6 on both, and virtualized both citrix server.
One is on each server. Virtualized one AD controller the oldest one and will be virtualizing the other one. Maximum users you would want on a citrix server would be We limit ours to 20 and have 16gb of ram on each of our 15 servers. Check your load evaluators to make sure they are not the problem. Having no available servers due to login requests can cause similar issues.
If they are, no new login requests will be able to be processed on that server. If you have roaming profiles or desktops I would look at the disk IO usage and network of the server that hosts the profiles.
I believe roaming profiles are not on. I was going to do redirected profiles but haven't done that yet. I will check now but the only thing I think they have is a home directory.
Definitely check on the roaming profiles. Bloated profiles can cause massive login slowdowns. Another good test would be to determine if a brand new created test user has the same slow issue or if it's fast to start with.
Also, I noticed now server installs are only Standard, so there goes the ram. They are only using 32GB of ram. Hotfix R06 is the latest for XenApp 6. If you're not comfortable with the latest then R05 is stable. That said I doubt that hotfix level is the issue. You mention when the classes are full it's slow. So, when class if full and you rdp to the server console is it slow at console?
When there is no load at all then does it run well from thin clients? Interested in how you limited yours to Interesting, they removed it from downloads. Now I was wondering, is it possible to create a report of let's say the top 50 users that take the most CPU cycles over a certain period?
You will be able to leave a comment after signing in. Welcome to the Citrix Discussions. Our site does not support outdated browser or earlier versions. To use our site, please take one of the following actions:. Jump to content. Learn more. Upvote if you also have this question or find it interesting. Follow, to receive updates on this topic. Sign in to follow this Followers 0.
Windows max users per vm? Martijn Kools Martijn Kools Aficionado Members posts. This is known as a Hosted Shared Desktop. The last 3 versions of XenApp have offered application streaming, also known as Application Virtualization. This replaced the application isolation feature that was available in some previous versions of XenApp.
By profiling an application using the Citrix Streaming Profiler you can stream the application down to a target Operating Systems without having to install anything apart from the Citrix Offline Plug-in. With Application Streaming you have the option of streaming the application to the client device, or to a XenApp server. If you stream to a client device it will run locally on that device and consume local resources CPU, memory etc , if you stream to a XenApp server it will run on the XenApp server and be accessed over ICA just like a traditional XenApp server-installed application.
Streamed applications are cached on the target operating system and therefore only pulled across the network on first run or when the central package is updated. You install the Citrix client software once and then you can deploy pretty much any application to any machine without having to ever visit them again.
Because all the processing is done on the XenApp servers you can deploy apps that would potentially not run on older desktops. If you are considering thin clients you can potentially run all of your users on XenApp and get rid of the maintenance costs associated with PC Operating Systems and hardware.
Citrix streamed applications execute locally on the target Operating System within a sandbox isolation environment.
0コメント