Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Product Name

CIS-CAT Pro Dashboard

Product Version

v3.x.x+

Date



Problem

Info

The imports to my Dashboard instance were initially very fast, ~20 seconds/report. However, after several thousand imports the import time increases to as much as [for example] 9 minutes per report. 

Solution

In this order, please first:

  1. Increase the Java Memory Pool by navigating to C:\Program Files\CCPD\CIS-CAT Pro Dashboard.vmoptions or usr/local/CCPD/CIS-CAT Pro Dashboard.vmoptions and double this number or more.

    1. Every environment is different and you may need to experiment with a higher number and then decrease to find the right spot for your uploads

  2. Compress/ zip the reports sent to Dashboard. If you have not already, in your Assessor-CLI.properties file, located in your Assessor-CLI\config directory around line 108 change this from false to true

    Code Block
    # Allow for assessment reports to be zipped/compressed when they are sent to the Dashboard via a POST request 
    # This property is only supported with Dashboard version 1.1.9 or higher. 
    ciscat.zip.post.files=true
    1. Restart the CCPD and MariaDBservices and test

  3. Members have found that import times for a multitude of reports has been greatly improved with a modification to the my.ini file

    1. Stop CCPD and MariaDB services

    2. If desired: Create a backup of the file, rename or remove backup from dir.

      1. C:\Program Files\CCPD\mariaDB\server\my.ini

    3. Open the my.ini file in a text editing program, add 2 lines to the my.inias shown below

      Code Block
      [mysqld]
      datadir=C:/Program Files/CCPD/mariaDB/server
      innodb-buffer-pool-size=16G
      max_allowed_packet=512M
    4. Save the file

    5. Restart the CCPD and MariaDBservices

Note

One member noticed that the RAM usage on the Dashboard server would spike to 100% and the CCPD service would intermittently stop. By putting in the "innodb-buffer-pool-size=16G" they were not allotting enough RAM for other system tasks. This member updated the my.ini file with:

innodb-buffer-pool-size=12G

This lower buffer pool size was more stable for this specific end-user.

Keywords;

Content by Label

Filter by label (Content by label)
showLabelsfalse
showSpacefalse
cqllabel = "sbp_fer"

Copyright © 2024

Center for Internet Security®