Hardware requirements
Black Duck hardware scaling guidelines
For scalability sizing guidelines, see Black Duck Hardware Scaling Guidelines.
Black Duck database
bds_hub)
unless directed to do so by a Black Duck Technical Support representative. Be sure to
follow appropriate backup procedures. Deletion of data will cause errors ranging
from UI problems to complete failure of Black Duck to start. Black Duck Technical
Support cannot recreate deleted data. If no backups are available, Black Duck will
provide support on a best-effort basis.Disk space requirements
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.
Black Duck Software recommends monitoring disk utilization on Black Duck servers to prevent disks from reaching capacity which could cause issues with Black Duck.
BDBA scaling
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 binaryscanner replica
-
One 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 binaryscanner replicas,
-
Two additional CPUs for PostgreSQL, and
-
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).