...
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 page has been retired, please click here for the for compatibility and support schedules on the Synopsys Software Integrity Group Documentation Portal.
| Redirect | ||||
|---|---|---|---|---|
|
Synopsys Black Duck Release |
|---|
2022.10.0 |
| Info |
|---|
The performance data below was gathered using Black Duck 2022.10.0 with reduced signature scan persistence (default) and Synopsys Detect 8.0.0. SPH values are calculated using a mix of signature scans, package manager detector scans and rapid scans. Average scan sizes vary from customer to customer so exact SPH throughput is highly customer specific. These metrics were gathered from Google Cloud Platform, which provides different database read/write IOPS for different configurations. |
Name | Scans/Hour | SPH % Increase | APIs/Hour | Project Versions | IOPS | Black Duck Services | PostgreSQL | Total |
10sph |
50 | 400% | 2.5k | 10k | Read: 15,000 | CPU: 12 core | CPU: 2 core | CPU: 14 core | |
120sph | 120 | 0% | 3k | 13k | Read: 15,000 | CPU: 13 core | CPU 4 core | CPU: 17 core |
250sph |
300 | 20% | 7.5k | 15k | Read: 15,000 | CPU: 17 core | CPU: 6 core | CPU: 23 core | |
500sph |
650 | 30% | 18k | 18k | Read: 15,000 | CPU: 28 core | CPU: 10 core | CPU: 38 core | |
1000sph |
1400 | 40% | 26k | 25k | Read: 25,000 | CPU: 47 core | CPU: 18 core | CPU: 65 core | |
1500sph |
1600 | 6% | 41k | 28k | Read: 25,000 | CPU: 66 core | CPU: 26 core | CPU: 92 core | |
2000sph |
2300 | 15% | 50k | 35k | Read: 60,000 | CPU: 66 core | CPU: 34 core | CPU: |
100 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 | 1050 | CPU: 2 core Memory: 8 GB | 2654 | 3185 |
120sph | 120 | CPU: 4 core Memory: 16 GB | 5338 | 6406 |
250sph | 250300 | CPU: 6 core Memory: 24 GB | 8018 | 9622 |
500sph | 500650 | CPU: 10 core Memory: 40 GB | 13377 | 16053 |
1000sph | 10001400 | CPU: 18 core Memory: 72 GB | 24129 | 28955 |
1500sph | 15001600 | CPU: 26 core Memory: 104 GB | 34880 | 41857 |
2000sph | 20002300 | CPU: 34 core Memory: 136 GB | 45600 | 54720 |
...