IBM Security Guardium

 View Only

  • 1.  Guardium Agent Resource Utilization (CPU, Memory etc.) on Database server

    Posted Mon February 22, 2021 10:35 AM
    Guardium Gurus,

    I am looking for performance matrix information in terms of how much minimum resources consumption is there by an Guardium agent in terms of CPU, Memory, Disk, I/O.

    Looked for the online IBM documentation but could not find any detailed information or some sort of performance matrix in terms of min resources
    usage by an Agent.

    Looking for information on below platforms for below technologies:

    DB2 LUW - AIX,Linux SUSE
    Oracle - AIX, Linux SUSE, Solaris
    MSSQL - Windows

    Did someone gathered these details in past and would like to share it please?

    ------------------------------
    Rohit Goyal
    ------------------------------


  • 2.  RE: Guardium Agent Resource Utilization (CPU, Memory etc.) on Database server

    Posted Thu July 27, 2023 10:34 AM

    https://docplayer.net/7567382-Guardium-s-tap-application-note.html

    Non-Intrusiveness
    Non-intrusiveness is achieved through the S-TAP's kernel components. A database makes system calls which the S-TAP
    monitors. Therefore, there are never any changes that need to be made to the database or the way that clients connect to
    the database. Because S-TAP utilizes kernel modules/drivers, resource utilization is also minimized and the overall impact
    to the server is minimal. S-TAP has been deployed on production servers with as many as 128 cores with negligible
    performance impact
    1
    .
    Defining precisely how many resources an S-TAP will take is difficult since it depends on application behavior and on the
    monitoring policy (how much of the database activity needs to be monitored). As a rule-of thumb, S-TAP will not consume
    more than an average of 5% of server resources. Through filtering policies, this can be reduced further for servers that are
    running close to 100% utilization (see section below).
    The S-TAP's memory footprint is very small. It will typically consume 20MB of RAM. Additionally, S-TAP maintains a
    buffer that is a memory-mapped file which is used for cases where there is no connectivity to any of the Guardium servers
    (see below). This will show up as RAM that is used by S-TAP but it is really a memory mapped file. The size of this file is
    configurable through guard_tap.ini and is typically set to 100MB.


    ------------------------------
    Elmer Vargas Cartagena
    especialista de software
    datec ltda.
    santa cruz
    (7) 631-8932
    ------------------------------

    Original Message


  • 3.  RE: Guardium Agent Resource Utilization (CPU, Memory etc.) on Database server

    Posted Thu July 27, 2023 10:34 AM
    Non-Intrusiveness
    Non-intrusiveness is achieved through the S-TAP's kernel components. A database makes system calls which the S-TAP
    monitors. Therefore, there are never any changes that need to be made to the database or the way that clients connect to
    the database. Because S-TAP utilizes kernel modules/drivers, resource utilization is also minimized and the overall impact
    to the server is minimal. S-TAP has been deployed on production servers with as many as 128 cores with negligible
    performance impact
    1
    .
    Defining precisely how many resources an S-TAP will take is difficult since it depends on application behavior and on the
    monitoring policy (how much of the database activity needs to be monitored). As a rule-of thumb, S-TAP will not consume
    more than an average of 5% of server resources. Through filtering policies, this can be reduced further for servers that are
    running close to 100% utilization (see section below).
    The S-TAP's memory footprint is very small. It will typically consume 20MB of RAM. Additionally, S-TAP maintains a
    buffer that is a memory-mapped file which is used for cases where there is no connectivity to any of the Guardium servers
    (see below). This will show up as RAM that is used by S-TAP but it is really a memory mapped file. The size of this file is
    configurable through guard_tap.ini and is typically set to 100MB.


    ------------------------------
    Elmer Vargas Cartagena
    especialista de software
    datec ltda.
    santa cruz
    (7) 631-8932
    ------------------------------

    Original Message


  • 4.  RE: Guardium Agent Resource Utilization (CPU, Memory etc.) on Database server

    Posted Tue August 01, 2023 08:48 AM

    Hi Rohit

    This official documentation informs about CPU consumption.
    https://www.ibm.com/docs/en/guardium/11.5?topic=linux-unix-s-tap-users-guide

    Regarding disk-
    https://www.ibm.com/docs/en/guardium/11.5?topic=prerequisites-linux-unix-disk-space-requirements-s-tap

    Regarding Memory- (might need a dedicated expert to explain this)
    There is no clear indication if S-TAP is going to use the server allocated memory directly.
    It depends on buffer_mmap_file value.
    https://www.ibm.com/docs/en/guardium/11.5?topic=parameters-linux-unix-general
    The documentation is not very clear on this.





    ------------------------------
    Sachin Marawar
    ------------------------------

    Original Message