Synopsys Black Duck Release |
|---|
2022.4.0 |
As of version 2022.4.0, the minimum recommended hardware requirements increased from 7 CPU cores & 28.5GB of RAM to 12 CPU cores and 37 GB of RAM. You can still manually change the hardware requirements and resource allocation using the provided helm charts or swarm configuration files. However, the current Black Duck default templates match the new recommendations. For the short to medium term we expect Black Duck to still be able to run successfully on the lesser requirements, but this may change over time. In the future, Black Duck will no longer be officially supporting nor testing with the older hardware specification. Customers who do not have available hardware to meet the new requirements will either need to add additional hardware or modify the orchestration files manually before updating to 2022.4.0.
This new guidance is based current Black Duck 2022.2.0 architecture. It is possible this guidance will be further refined for the 2022.4.0 or subsequent releases. If you have any questions or concerns, please reach out to Product Management.
Name | Scans/Hour | Black Duck Services | PostgreSQL | Total |
10sph | 10 | CPU: 12 core | CPU: 2 core | CPU: 14 core |
120sph | 120 | CPU: 13 core | CPU 4 core | CPU: 17 core |
250sph | 250 | CPU: 17 core | CPU: 6 core | CPU: 23 core |
500sph | 500 | CPU: 28 core | CPU: 10 core | CPU: 38 core |
1000sph | 1000 | CPU: 47 core | CPU: 18 core | CPU: 65 core |
1500sph | 1500 | CPU: 66 core | CPU: 26 core | CPU: 92 core |
2000sph | 2000 | CPU: 66 core | CPU: 34 core | CPU: 99.5 core |
PostgreSQL Settings
Customers using the PostgreSQL container will need to set the values manually using ALTER SYSTEM,
and changes to shared_buffers won't take effect until after the next time that PostgreSQL is restarted.
These settings apply to both Kubernetes and Swarm installations.
Name | Scans/Hour | PostgreSQL CPU/Memory | shared_buffers (MB) | effective_cache_size (MB) |
|---|---|---|---|---|
10sph | 10 | CPU: 2 core Memory: 8 GB | 2654 | 3185 |
120sph | 120 | CPU: 4 core Memory: 16 GB | 5338 | 6406 |
250sph | 250 | CPU: 6 core Memory: 24 GB | 8018 | 9622 |
500sph | 500 | CPU: 10 core Memory: 40 GB | 13377 | 16053 |
1000sph | 1000 | CPU: 18 core Memory: 72 GB | 24129 | 28955 |
1500sph | 1500 | CPU: 26 core Memory: 104 GB | 34880 | 41857 |
2000sph | 2000 | CPU: 34 core Memory: 136 GB | 45600 | 54720 |
Note: The amount of required disk space is dependent on the number of projects being managed, so individual requirements can vary. Consider that each project requires approximately 200 MB.
BDBA scaling is done by adjusting the number of binaryscanner replicas and by adding PostgreSQL resources based on the expected number of binary scans per hour that will be performed. For every 15 binary scans per hour, add the following:
One
binaryscannerreplicaOne CPU for PostgreSQL
4GB memory to PostgreSQL
If your anticipated scan rate is not a multiple of 15, round up. For example, 24 binary scans per hour would require the following:
Two
binaryscannerreplicasTwo additional CPUs for PostgreSQL
8GB additional memory for PostgreSQL
This guidance is valid when binary scans are 20% or less of the total scan volume (by count of scans).
Black Duck Software recommends monitoring disk utilization on Black Duck servers to prevent disks from reaching capacity which could cause issues with Black Duck.
Note: Installing Black Duck Alert requires 1 GB of additional memory.