The best way to increase performance is to reduce work, in this \u00a0first step it’s to reduce the hard disk read by reading virtual hard disk files (VHD’s). This can be achieved by make use of the Windows disk cache, this approach is possible on physical PVS servers and as well on virtualized PVS servers on any hypervisor.\u00a0Using the Windows disk cache means that files which are read from disk, are cached in Standby memory of the Server.
\n(If you are using XenServer as hypervisor have a look to the IntelliCache feature,\u00a0http:\/\/blog.citrix24.com\/how-does-intellicache-work. )<\/p>\n
To make use of the file cache you need:<\/p>\n
- \n
- The vDisk on local<\/span> drives, no CIFS share, no NFS share.<\/li>\n
- A plenty of memory to the PVS.<\/li>\n<\/ul>\n
Having the vDisk’s on local disks is not the common way to work with PVS, keep in mind that you have to synchronize the files on all servers in PVS farm.<\/p>\n
You can check if the file cache is used properly by having a look in the resource\u00a0manager. If you have nearly no free memory and have a lot of use standby memory it’s a good sign:<\/p>\n
![\"ressourcemgr\"](\"http:\/\/blog.sachathomet.ch\/wp-content\/uploads\/2014\/01\/ressourcemgr.png\")
<\/a><\/p>\nTo have a deep dive look in the cache use RamMap and keep an eye to File Summary:<\/p>\n
![\"rammap-vhd\"](\"http:\/\/blog.sachathomet.ch\/wp-content\/uploads\/2014\/01\/rammap-vhd.png\")
<\/a><\/p>\n<\/p>\n
#2. Use Target Device Write Cache on Ram<\/strong><\/p>\n
The second second way to increase performance is to use fastest possible storage, hard disk drives are quite\u00a0fast today, solid state disks are faster but Ram is still the fastest memory. Because we need on the Target device only the Write Cache it doesn’t matter that the Ram is a transient memory.<\/p>\n
A short performance comparison:<\/strong><\/p>\n
With AS SSD Benchmark you can measure the speed of your disk. <\/span><\/p>\n
Target Device with WriteCache on Ram:
\n<\/span>![\"assd_benchmark_CacheRam\"](\"http:\/\/blog.sachathomet.ch\/wp-content\/uploads\/2014\/01\/assd_benchmark_CacheRam.png\")
<\/a><\/p>\nTarget Device with WriteCache on local disk:<\/span>
\n![\"assd_benchmark_Cache_TargetDisk\"](\"http:\/\/blog.sachathomet.ch\/wp-content\/uploads\/2014\/01\/assd_benchmark_Cache_TargetDisk.png\")
<\/a><\/p>\n( AS SSD Benchmark is Freeware and you can download and donate on:\u00a0http:\/\/www.alex-is.de\/PHP\/fusion\/downloads.php?cat_id=4&download_id=9<\/a>\u00a0)<\/p>\n
Keep in sight the Memory<\/strong><\/p>\n
When you working with Write Cache in the Target device Ram you must \u00a0appreciate the dangers of it … If you are running out of WriteCache the Target Device, perhaps a XenApp server with 50 users on it, will reboot\u00a0<\/span>immediately\u00a0.
\n(By the way … \u00a0Citrix Provisioning Services 7.1 offers a great new feature, it’s the possibility to Cache to Ram with overflow to hard disk. Do not use it … it doesent work proper! Waiting for a hotfix.)<\/span><\/p>\n- \n
- Plan the amount of real used Memory:Think how much of the Ram you will use for WriteCache, give as much as possible and consider the real memory usage of a fully loaded server. e.g. if you have a XenApp server as Target device with 16GB of Memory you can allocate 6GB for WriteCache and have still 10GB Memory for the XenApp servers. If you have special memory hungry application on the server you need maybe an other\u00a0segmentation. It doesn’t exists a recipe, have a look on your currently productive servers about the used memory.<\/li>\n<\/ul>\n
- \n
- Reboot your Target device\u00a0periodically to reset the used cache.<\/li>\n<\/ul>\n
- \n
- Reduce usage of Write Cache by redirecting as much as possible to an other disk drive, of course this is only possible if you still have a local disk attached to the Target Device.Good candidates to redirect are:\n
- \n
- Printer Spooler<\/li>\n
- Pagefile<\/li>\n
- EventLog<\/li>\n
- EdgeSight database<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n
- \n
- Monitor your Write Cache, \u00a0a way to do this is e.g. using this small Powershell script on the PVS server with a scheduled task:
\n(If you have PVS 7.1 with the newest Hotfixes<\/span> I recommend to use WriteCache on Ram with overflow to hard disk)<\/span><\/li>\n<\/ul>\n\r\n#========================================================================\r\n# Created on: 09.01.2014\r\n# Created by: Sacha T. blog.sachathomet.ch\r\n# Filename: Citrix-PVS-Get-Targetdevice-WriteCacheSize.ps1\r\n#\r\n# Descritpion: This script query the used write cache of the PVS farm\r\n# connected target devices and write an event log entry if\r\n# a target device exceed a definec % value of cache.\r\n#\r\n# Prerequisite: Script must run on a PVS server, where MCLI snap-in is registered.\r\n#\r\n# Register SnapIn with command: C:\\WINDOWS\\Microsoft.NET\\Framework64\r\n# \\v2.0.50727\\InstallUtil.exe 'C:\\Program Files\\Citrix\\Provisioning S\r\n# ervices Console\\McliPSSnapIn.dll'\r\n#\r\n# Call by : Scheduled Task all e.g. all 5 min.\r\n#\r\n#========================================================================\r\n$thresholdInformation=55 # define the Threshold in %\r\n$thresholdWarning=70 # define the Threshold in %\r\nAdd-PSSnapin -Name McliPSSnapIn -ErrorAction SilentlyContinue\r\n$pvsdevices = mcli-get device -f deviceName | Select-String deviceName\r\nforeach($target in $pvsdevices)\r\n{\r\n $target | Select-String deviceName\r\n $_targetshort = $target -replace "deviceName: ",""\r\n\r\n mcli-get deviceinfo -p devicename=$_targetshort -f status\r\n\r\n $devicestatus = mcli-get deviceinfo -p devicename=$_targetshort -f status\r\nif ($devicestatus[4].TrimStart("status: ") -replace ",","." -gt $thresholdWarning)\r\n{Write-Host "WARNING: The Write Cache of the PVS-Target device $_targetshort exceeded $thresholdWarning %! Intervention is needed" -foregroundcolor "red"\r\n#do here what you need, email, eventlog etc ...\r\n write-eventlog -logname Application -source StreamProcess -eventID 3001 -entrytype Warning -message "A PVS target device, $_targetshort, exceeded the threshold ($thresholdWarning %) !" -category 1 -rawdata 10,20\r\n }\r\n\r\n elseif ($devicestatus[4].TrimStart("status: ") -replace ",","." -gt $thresholdInformation)\r\n{Write-Host "INFORMATION: The Write Cache of the PVS-Target device $_targetshort exceeded $thresholdInformation %! " -foregroundcolor "yellow"\r\n#do here what you need, email, eventlog etc ...\r\n write-eventlog -logname Application -source StreamProcess -eventID 3001 -entrytype Information -message "A PVS target device, $_targetshort, exceeded the threshold ($thresholdInformation %) !" -category 1 -rawdata 10,20\r\n }<\/pre>\n#3. Avoid if possible cross Data centre streaming\u00a0<\/strong><\/p>\n
- \n
- If you have different subnet’s, make use of subnet affinity in the load balancing configuration on the vDisk.<\/li>\n
- If you have one subnet over more data centres, create a store with the vDisk for each data centre and let only provide servers from the\u00a0corresponding data centre this store. With this way you can still switch fast to a cross data centre configuration in a case of a PVS server outage in a data centre.<\/li>\n
- <\/li>\n<\/ul>\n
4#. Use all exiting best practice guides for tuning:
\n(for all what I’ve forget here … )<\/strong><\/p>\ne.g. : http:\/\/blogs.citrix.com\/2010\/11\/05\/provisioning-services-and-cifs-stores-tuning-for-performance<\/a> \u00a0and\u00a0http:\/\/support.citrix.com\/article\/CTX127549<\/a><\/p>\n
<\/p>\n
ff<\/p>\n","protected":false},"excerpt":{"rendered":"
Citrix Provisioning Services is in my point of view an\u00a0incomparable way to deliver a Software image to a \u00a0system. It’s not a kind of an known enterprise software deployment, rather it’s a way to stream a virtual disk during runtime to hardware. Beside of PVS, the acronym of Provisioning Services. This article doesn’t explain what’s […]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[4,1],"tags":[14,34],"class_list":["post-73","post","type-post","status-publish","format-standard","hentry","category-design","category-uncategorized","tag-citrix","tag-provisioningservices"],"translation":{"provider":"WPGlobus","version":"3.0.2","language":"de","enabled_languages":["en","de"],"languages":{"en":{"title":true,"content":true,"excerpt":false},"de":{"title":false,"content":false,"excerpt":false}}},"jetpack_featured_media_url":"","_links":{"self":[{"href":"https:\/\/blog.sachathomet.ch\/de\/wp-json\/wp\/v2\/posts\/73","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blog.sachathomet.ch\/de\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.sachathomet.ch\/de\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.sachathomet.ch\/de\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.sachathomet.ch\/de\/wp-json\/wp\/v2\/comments?post=73"}],"version-history":[{"count":2,"href":"https:\/\/blog.sachathomet.ch\/de\/wp-json\/wp\/v2\/posts\/73\/revisions"}],"predecessor-version":[{"id":962,"href":"https:\/\/blog.sachathomet.ch\/de\/wp-json\/wp\/v2\/posts\/73\/revisions\/962"}],"wp:attachment":[{"href":"https:\/\/blog.sachathomet.ch\/de\/wp-json\/wp\/v2\/media?parent=73"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.sachathomet.ch\/de\/wp-json\/wp\/v2\/categories?post=73"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.sachathomet.ch\/de\/wp-json\/wp\/v2\/tags?post=73"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
- Monitor your Write Cache, \u00a0a way to do this is e.g. using this small Powershell script on the PVS server with a scheduled task:
- Reduce usage of Write Cache by redirecting as much as possible to an other disk drive, of course this is only possible if you still have a local disk attached to the Target Device.Good candidates to redirect are:\n
- Reboot your Target device\u00a0periodically to reset the used cache.<\/li>\n<\/ul>\n
- A plenty of memory to the PVS.<\/li>\n<\/ul>\n