CMDB Sizing Guidelines

Database sizing guidelines

The table below provides baseline database sizing estimates depending on your operational context. The PostgreSQL database stores configuration items (CIs), relationships/topology mappings, attributes, and audit history logs.

Context	Small environment	Medium environment	Large environment
Configuration Items (CIs)	Up to 10K	Up to 100K	1M or more
PostgreSQL CI tables	~100 Mo	~1.2 Go	~15 Go
Number of relationships	Up to 50K	Up to 500K	5M or more
PostgreSQL relation tables	~50 Mo	~600 Mo	~8 Go
Audit & history records	Up to 200K	Up to 2M	20M or more
PostgreSQL history tables	~350 Mo	~3.5 Go	~40 Go
Estimated total storage	~5 Go	~20 Go	~100 Go or above

Note

Total storage estimations include table data, indexes, foreign keys, and operational write-ahead logging (WAL) headroom. Audit log retention policies directly impact long-term database storage growth.

Sizing for concurrent users on Likpi CMDB consoles

Context	Small environment	Medium environment	Large environment
Registered end users	25	100	300 or more
Concurrent active sessions	10	35	100 or more
Administrator users	2	5	10

Note

For scalable, multi-tenant, and complex clustered environments, please contact the Likpi support for custom sizing guidelines.