Support Center > Search Results > SecureKnowledge Details
Memory utilization in R80.10 Security Gateway / StandAlone Technical Level
Solution

(1) R80.10 Security Gateway

R80.10 Security Gateway introduces optimizations of 20%-30% in overall memory utilization for NGTP and HTTPS Inspection.

Show / Hide example numbers

The following are example numbers for some appliances in Security Gateway configuration.
The only purpose of these numbers is to demonstrate the difference in memory utilization between R80.10 and R77.30 versions.
The real memory utilization measured on your appliance will vary depending on your specific configuration
(the enabled software blades, the configured number of CoreXL FW instances, traffic amount and blend, etc.)

Appliance
model
Version
and
Delta(1)
Used
Kernel
Memory(2)
[MB]
Used
Memory(3)
[MB]
5200 R77.30 918 2266
R80.10 881 1822
Delta [MB] -37 -444
Delta [%] -4.03% -19.59%
5600 R77.30 1187 2940
R80.10 1050 2082
Delta [MB] -137 -858
Delta [%] -11.54% -29.18%
15400 R77.30 2522 5489
R80.10 2059 4147
Delta [MB] -463 -1342
Delta [%] -18.36% -24.45%

Notes:

  1. "Delta" denotes a difference between the memory utilization in R80.10 and in R77.30 (i.e., Delta = "R80.10 utilization" - "R77.30 utilization").
  2. "Used Kernel Memory" denotes a FireWall kernel memory consumption,
    which can be viewed in the output of the "fw ctl pstat" command - refer to the "(3) General Notes" section below.
  3. "Used Memory" denotes an overall memory consumption,
    which can be viewed in the output of the "top" command - refer to the "(3) General Notes" section below.

 

(2) R80.10 StandAlone

R80.10 StandAlone introduces a growth of 10%-30% in overall memory utilization for NGTP and HTTPS Inspection.

Notes:

  • StandAlone refers to a deployment where Security Gateway and Security Management Server are running on the same appliance.

  • Growth in overall memory utilization is attributed to the new Security Management architecture introduced in R80 version.

  • R80.10 Security Management Server introduces log indexing engine for enhanced log searching capabilities.
    Log indexing increases an overall memory utilization on top of the 10%-30% growth described above.
    Running without the new log indexing is supported in R80.10 StandAlone, which would provide the same functionality as in Smart View Tracker in R77.x and below releases.
    Refer to the R80.10 Logging and Monitoring Administration Guide - chapter "Getting Started" - section "Deploying Logging" - subsection "Disabling Log Indexing".

Show / Hide example numbers

The following are example numbers for some appliances in StandAlone configuration.
The only purpose of these numbers is to demonstrate the difference in memory utilization between R80.10 and R77.30 versions.
The real memory utilization measured on your appliance will vary depending on your specific configuration
(the enabled software blades, the configured number of CoreXL FW instances, traffic amount and blend, etc.)

Appliance
model
Version
and
Delta(1)
Used
Kernel
Memory(2)
[MB]
Used
Memory(3)
[MB]
5200 R77.30 917 3074
R80.10 879 4013
Delta [MB] -38 939
Delta [%] -4.14% 30.55%
5600 R77.30 1197 3838
R80.10 1056 4743
Delta [MB] -141 905
Delta [%] -11.78% 23.58%
15400 R77.30 2460 5631
R80.10 2003 6122
Delta [MB] -457 491
Delta [%] -18.58% 8.72%
  1. "Delta" denotes a difference between the memory utilization in R80.10 and in R77.30 (i.e., Delta = "R80.10 utilization" - "R77.30 utilization").
  2. "Used Kernel Memory" denotes a FireWall kernel memory consumption,
    which can be viewed in the output of the "fw ctl pstat" command - refer to the "(3) General Notes" section below.
  3. "Used Memory" denotes an overall memory consumption,
    which can be viewed in the output of the "top" command - refer to the "(3) General Notes" section below.

 

(3) General Notes

  • R80.10 Security Gateway optimizations numbers are compared with R77.30 Security Gateway, which already introduced memory optimizations as described in
    sk109772 - R77.30 NGTP, NGTX and HTTPS Inspection performance and memory consumption optimization.

  • Overall memory consumption can be viewed in the output of the "top" command (refer to the "Mem:" line).

    Example excerpt from the command output:

    Tasks: 118 total,   2 running, 116 sleeping,   0 stopped,   0 zombie
    Cpu(s):  0.2%us,  0.2%sy,  0.0%ni, 98.8%id,  0.1%wa,  0.4%hi,  0.3%si,  0.0%st
    Mem:   8240020k total,  8048480k used,   191540k free,   268024k buffers
    Swap:  8385920k total,       60k used,  8385860k free,  1538520k cached
    
      PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND
        1 admin     15   0  2044  724  624 S    0  0.0   0:01.56 init
    
  • FireWall kernel memory consumption can be viewed in the output of the "fw ctl pstat" command (refer to the "Memory used:" line).

    Example excerpt from the command output:

    System Capacity Summary:
      Memory used: 9% (149 MB out of 1508 MB) - below watermark
      Concurrent Connections: Not Available
      Aggressive Aging is enabled, not active
    

 

Revision History

Show / Hide revision history

Date Description
02 Oct 2017
  • First release of this article.

Give us Feedback
Please rate this document
[1=Worst,5=Best]
Comment