0

High cpu and read activity on the network adapter

Hi,

We are experiencing extremely high CPU and a lot of READ activity on the network-adapter. We think because uberAgent is scanning the disk, this is also stressing the connection to the PVS server.

We already modified the settings as suggested in the other posts on here:

[ProductComponents]
EnableESA = true

[ProcessStartupSettings]
EnableCalculateHash = false

We performed multiple reboots and service restarts but to no avail.  When uberagent service is stopped, everything turns back to normal.

Please advice.

6 comments

  • 0
    Avatar
    Dominik Britz

    Hi Sven,

    Could please also test this setting?

    [NetworkTargetPerformanceProcess_Config]
    NetworkDriverEnabled = false
  • 0
    Avatar
    Chris Marreel

    Hi Dominik,

    We have already added to the uberAgent config the following:

    [NetworkTargetPerformanceProcess_Config]
    NetworkDriverEnabled = false

    [ProcessStartupSettings]
    EnableCalculateHash = false

    And restarted the UberAgent service, but still we experience from time to time long periods where we notice that NETWORK READ is pushed to 90-120Mbps, and at the same time we notice in the task manager that 'System' and 'System interrups' are extreemly high causing the xenApp-worker to become extreemly slow.

    And from the moment we stop the 'UberAgent'-service the XenApp-worker is acting normally again.

    This is a XenApp 1912 CU2 running on W2K19, where we use Citrix PVS (also 1912 CU2) running on a XenServer 8.2 hypervisor.  And we use WEM 2103 for mainly memory optimization.

    We assume it must be uberagent-related, as we don't experience the issue if the uberagent-service is stopped.

    But from the moment we start the service after a while we see the behavior again.

    What are the next steps we can take ?

    P.S. the UberAgent-client is version 6.0.0.4171 (I assume the latest at the moment).

  • 0
    Avatar
    Chris Marreel

    Hi Dominik, 

    My college and co-worker Sven Goossens triggered me that the new UberAgent 6.1 is available.

    So I have upgraded my master-image with this new version, and during the next night all 16 XenApp-workers will be rebooted and will start with the new 6.1 endpoint agent.  So we will evaluate from tomorrow with this new version.  

    I will update this post with the results after some period of evaluation.

    Greetings,

      Chris Marreel

  • 0
    Avatar
    Dominik Britz

    Thanks for the info. I'll wait for your update.

  • 0
    Avatar
    Chris Marreel

    Hi Dominik,

    After one working-day and close following up, I can confirm the issue is gone.    This sounds good !

    We have a few UberAgent setups at customer-sites, all working with the 6.0 version, but only this one was experiencing that issue.  So its strange that we don't see that same behavior in the other setups, but I assume we will upgrade those 6.0-version to the newer 6.1 in the next weeks.

     

    Greetings,

      Chris Marreel

  • 0
    Avatar
    Dominik Britz

    Thanks, Chris,

    I'm closing this.

Please sign in to leave a comment.