![]() ![]() If you don’t have time or resources to do proper sizing, I highly recommend our consulting white paper describing advanced memory considerations for Provisioning Services ( CTX125126). When you ask any consultant about proper sizing of the PVS memory, you will probably either get answer “It depends” (don’t you love it?) or you will get calculations based on safe estimates. The reasons why PVS requires spare memory were already discussed in my previous article – it’s a service that is actually designed toleverage your unused memory. Yes, PVS is using memory (as a cheap caching mechanism), however that doesn’t mean that you need to build supercomputer to use Provisioning Services. There are a lot of misunderstanding and misconceptions about Provisioning Services – and one of them is that PVS requires a huge amounts of memory to work properly. You should already understand the concept of Windows caching manager. In first part, I’ve prepared the theoretical ground for the discussion about proper sizing of the memory. I’ve been extremely busy recently, so please accept my apologies it took so long to finish the second part of the blog post. I’m really surprised myself, but it’s been already 8 months since I wrote the first part of PVS internals. ![]() Citrix App Delivery and Security Service. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |