Solved

Allocate drive for Paging file when spec'ng Citrix PVS server?

Posted on 2014-01-28
7
2,407 Views
Last Modified: 2014-02-08
Hello there,

We are implementing Citrix PVS server to stream XenDeskop with Personal disk and Write cache drive.

My question since we will be using 2 x vDisk images for x 32 bit and x64 bit windows 7 OS, with approx 20 GB the size of vDisk each.

While spec'ng Provisioning server, do we need to allocate a separate drive for paging file?
PVS memory - 40 GB and Paging file drive = 1.5 x memory = 60 GB.

Is this a best practice?

Please advise.

Thanks and Regards
0
Comment
Question by:goprasad
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
7 Comments
 
LVL 9

Assisted Solution

by:Vijaya Reddy Pinnapa Reddy
Vijaya Reddy Pinnapa Reddy earned 72 total points
ID: 39814907
Please check this article for Page file best practices.
http://blogs.citrix.com/2011/12/23/the-pagefile-done-right/
0
 
LVL 37

Accepted Solution

by:
Carl Webster earned 214 total points
ID: 39814966
For PVS, if it has enough RAM, will not use the page file much if at all.  The vDisks that the PVS server streams will be cached in the PVS server's RAM.  The targets should be set to cache in device RAM or device hard drive.  That means there is no space taken up on the PVS server by the target's write cache.

If the write cache is set for target's hard disk then you will be using storage space for the target's write cache and again nothing goes to the PVS server.

You are over thinking this as page file stuff is old news and the old page file should be at least 1.5 times RAM is just bogus.

So no, your question is this is not best practice and I NEVER EVER worry about it in real life.
0
 
LVL 6

Assisted Solution

by:Brainstormer
Brainstormer earned 143 total points
ID: 39818737
I don't have a PVS server in front, so going off memory.

In PVS 6.x your choices are as follows:

Cache to RAM
Cache to Device HD <- This should be what you want, and the cache will be on the VM, not PVS servers
Cache to server (PVS)
....


In PVS 7.x your choices are as follows:

Cache to RAM
Cache to RAM with overflow to HD<- This should be what you want as 1st option.
Cache to Device HD <- This should be what you want as 2nd option, and the cache will be on the VM, not PVS servers
Cache to server (PVS)
....
0
Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
LVL 37

Assisted Solution

by:Carl Webster
Carl Webster earned 214 total points
ID: 39818865
"Cache to RAM with overflow to HD<- This should be what you want as 1st option."

Unfortunately this option does not work.

http://virtexperience.com/2013/11/05/pvs-7-1-ram-cache-with-overflow-to-disk/

There is a hotfix available as listed in the comments to the article but I have not heard if it is fixed yet.
0
 
LVL 6

Assisted Solution

by:Brainstormer
Brainstormer earned 143 total points
ID: 39818924
Interesting, I am testing it at a customer now. The author of that article as a followup article here http://virtexperience.com/2013/11/11/how-i-increased-iops-200-times-with-xenserver-and-pvs/.

Regardless, we are debating something that if or when it works will be the standard setting on most deployments. Hence I list as #1 in PVS 7.x with Cache to HD as #2. The author wants to know about cache size on PVS server (Cache to Server) which is not recommended compared to the above choices.

In conclusion, my recommendation still stands.
0
 
LVL 31

Assisted Solution

by:Cláudio Rodrigues
Cláudio Rodrigues earned 71 total points
ID: 39820987
Now it works. It was not working exactly as planned performance wise. As others pointed out normally a small virtual disk attached to the endpoint VM is enough to hold the paging file (depending on the project and RAM for the VM I use anywhere between 5 and 12GB for the virtual disk) and set the paging file to a fixed size.

For the PVS server itself, the key thing is to have a LOT of RAM so as Carl pointed out the vDisks can be cached as much as possible in RAM. So the paging file really is probably barely used and a couple gigs one will do it.

If using a CIFS file server to store the PVS images make sure it also has lots of RAM (I normally have the same amount of RAM on the File servers as I do on the PVS servers). And try to stick to SMB 3.0.


Cláudio Rodrigues
Microsoft MVP - RDS
Citrix CTP
0
 
LVL 37

Assisted Solution

by:Carl Webster
Carl Webster earned 214 total points
ID: 39837323
Citrix updated their article with regards to intermediate buffering.

http://support.citrix.com/article/CTX126042
0

Featured Post

On Demand Webinar: Networking for the Cloud Era

Did you know SD-WANs can improve network connectivity? Check out this webinar to learn how an SD-WAN simplified, one-click tool can help you migrate and manage data in the cloud.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Let’s list some of the technologies that enable smooth teleworking. 
ADCs have gained traction within the last decade, largely due to increased demand for legacy load balancing appliances to handle more advanced application delivery requirements and improve application performance.
How to install and configure Citrix XenApp 6.5 - Part 1. In this video tutorial we have explained step by step installation of Citrix XenApp 6.5 Server on Windows Server 2008 R2 is explained in this video. We have explained the difference between…
This demo shows you how to set up the containerized NetScaler CPX with NetScaler Management and Analytics System in a non-routable Mesos/Marathon environment for use with Micro-Services applications.

726 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question