Tag Archives: cpu

Citrix Netscaler VPX high CPU usage? almost 100%

I’m running a Citrix Netscaler VPX in my lab, and I just noticed that even though there is no connection, the CPU usage for this VPX is 100%.

You can change this behavior by doing the following:

On the left, go to System > Settings.

On the right, in the bottom of the second column, click Change VPX Configuration Settings.

Change the CPU Yield drop-down to YES, and click OK.

After making this change, you can see an immediate drop-off in CPU consumption.

Understanding Citrix Performance Issues

Bottleneck: provisioning services. Customers note there is excessive Network I/O and CPU utilization.
Bottleneck: vDisk fragmentation or server virtual instances. Customer notes there is excessive page file utilization and disk I/O.
Bottleneck: delays mounting new vDisks. Check for excessive Network and Disk I/O on delivery controllers.
Bottleneck: delivery controllers. Check for excessive historical CPU utilization.
Bottleneck: slow application enumeration. Check for excessive disk and network I/O on the data collectors.
Bottleneck: slow session creation noted within the director console: Check for historical CPU and Memoyr consumption, consider adding VCPU and memory when/where needed.
Bottleneck: higher than expected user logons. Check for high CPU and/or network utilization (not historical but may trend at random intervals). Add processing or new delivery controller if necessary to handle the expected loads.
Bottleneck: issues with local host cache (LHC). Disk and Page File I/O in excess can cause unanticipated issues with LHC. Alert and adjust when/where needed.
Bottleneck: Processor intensive apps. Check questionable servers for larger disk I/O and page file utilization. Consider adding more VCPU’s and/or memory to offset the demand on disk and page file.
Bottleneck: vDisk and/or Provisioning Services. Check for higher than normal CPU and/or Memory consumption as a deficiency will slow down the loading of vDisks and caching via Provisioning Services (PVS).
Bottleneck: Web interface authentication. Consider adding more memory and looking at network utilization trends. It may be necessary to either add more memory or to add an additional WI to your GSLB URL.
Bottleneck: slow PXE and vDisk. Check for memory and/or network utilization and consider addresssing depending on noted trends.
Bottleneck: target device latency. Check CPU and network I/O for spikes and/or trending issues.


"新加坡消息:AMD 已向英特尔发出挑战书,准备用自己的双核处理器与英特尔的双核处理器进行基准测试,一决性能高下。如果英特尔接受此项挑战提议,那么这次比试活动将于12月6 日在新加坡这个岛国举行。
由AMD 提出的这次双内核处理器比试活动将进行现场直播,公众预计,这次比试的平台将是AMD 当前最好的双内核处理器Opteron 800 系列或是200 系列处理器,与英特尔相对应的Intel x86 商用处理器平台之间的对决。
有关这次挑战活动的消息,是上周初被作为广告宣传单夹在当地报纸中公之于众,这也是由AMD 发起的,继8 月23日在美国的挑战活动后的又一次挑战。
AMD 东南亚地区销售与市场部副总裁,Bryan Low 在应ZDNet 亚洲记者的电子邮件采访时表示,本次挑战活动的目的就是“给消费者所关心的,相关处理器在计算能力及性能方面的信息,以便于他们能作出最佳选择。”
到目前为止,不管是在新加坡还是美国,英特尔都没有正式接受AMD 的挑战。截至发稿时为止,芯片市场的老大英特尔业也没有对事接受采访。"