Layer7 Privileged Access Management

Expand all | Collapse all

Seosd Process Utilization

Jump to Best Answer
  • 1.  Seosd Process Utilization

    Posted 05-23-2018 09:21 AM

    How much CPU utilization seosd process can cause on Unix endpoints?

  • 2.  Re: Seosd Process Utilization

    Posted 05-24-2018 12:58 PM

    Hello Narenda,


    The amount of CPU utilized by seosd has multiple factors, so it is hard to give a precise answer of how much it should be using at any given point in time. For example, seosd is consuming 0% CPU in my lab environment. However, the server is not used much, so seosd does not have the workload that it may have in a live environment.


    Here are some factors for seosd CPU utilization.

    1- Other programs installed on the server. Seosd follows system calls made by other programs, so a server with more programs installed, or a server that has higher utilized programs, will see seosd consuming more CPU.

    2- How many users are logged onto the server at any given time. Since seosd tracks every user's rights, a server with 2 users logged in will cause seosd lower usage than one with 10 users logged in.

    3- The version of seosd running on the server. Newer versions of seosd contain code changes that have improved seosd's performance, particularly when you compare 12.8 GA with 12.8 SP1.


    Are you having any particular issues with seosd causing CPU spikes and/or consuming high CPU for long periods of time?


    Kind Regards,

    Brian Rehder

    Senior Support Engineer

    CA Technologies

  • 3.  Re: Seosd Process Utilization

    Posted 06-07-2018 07:07 AM

    You are saying in point no. 1 "soesd follows system call made by other programs", can you please elaborate why seosd do this?

    Please describe what is the task seosd of process on server, it will help us to understand it better.

  • 4.  Re: Seosd Process Utilization
    Best Answer

    Posted 05-25-2018 08:36 AM

    A properly configured system, 3-4% CPU usage (total not 3-4% of one processor or core) is the norm/goal. This is the number we have been told, have seen in the field, and with testing in client environments. If you are seeing higher than this, you may need to adjust your ACL's and define some exclusions in the special program class.