diff --git a/layouts/shortcodes/dbm-mysql-agent-config-examples.en.md b/layouts/shortcodes/dbm-mysql-agent-config-examples.en.md
index 0deb328d02f0a..3ec49863c7f82 100644
--- a/layouts/shortcodes/dbm-mysql-agent-config-examples.en.md
+++ b/layouts/shortcodes/dbm-mysql-agent-config-examples.en.md
@@ -1,6 +1,7 @@
 ### One agent connecting to multiple hosts
 It is common to configure a single Agent host to connect to multiple remote database instances (see [Agent installation architectures](/database_monitoring/architecture/) for DBM). To connect to multiple hosts, create an entry for each host in the MySQL integration config.
-An agent with 4 CPUs and 16GB of RAM can monitor up to 30 databases with the same resources each.
+
+<div class="alert alert-info">Datadog recommends using one Agent to monitor no more than 30 database instances.<br /><br />Benchmarks show that one Agent running on a t4g.medium EC2 instance (2 CPUs and 4GB of RAM) can successfully monitor 30 RDS db.t3.medium instances (2 CPUs and 4GB of RAM).</div>
 
 ```yaml
 init_config:
diff --git a/layouts/shortcodes/dbm-postgres-agent-config-examples.en.md b/layouts/shortcodes/dbm-postgres-agent-config-examples.en.md
index d54b42c9e70d1..d39b02a5e753a 100644
--- a/layouts/shortcodes/dbm-postgres-agent-config-examples.en.md
+++ b/layouts/shortcodes/dbm-postgres-agent-config-examples.en.md
@@ -1,6 +1,8 @@
 ### One agent connecting to multiple hosts
 It is common to configure a single Agent host to connect to multiple remote database instances (see [Agent installation architectures](/database_monitoring/architecture/) for DBM). To connect to multiple hosts, create an entry for each host in the Postgres integration config.
-An agent with 4 CPUs and 16GB of RAM can monitor up to 30 databases with the same resources each.
+
+<div class="alert alert-info">Datadog recommends using one Agent to monitor no more than 30 database instances.<br /><br />Benchmarks show that one Agent running on a t4g.medium EC2 instance (2 CPUs and 4GB of RAM) can successfully monitor 30 RDS db.t3.medium instances (2 CPUs and 4GB of RAM).</div>
+
 ```yaml
 init_config:
 instances:
diff --git a/layouts/shortcodes/dbm-sqlserver-agent-config-examples.en.md b/layouts/shortcodes/dbm-sqlserver-agent-config-examples.en.md
index a3468a03cdf77..61a4481c04cf3 100644
--- a/layouts/shortcodes/dbm-sqlserver-agent-config-examples.en.md
+++ b/layouts/shortcodes/dbm-sqlserver-agent-config-examples.en.md
@@ -121,7 +121,9 @@ instances:
 
 ### One Agent connecting to multiple hosts
 It is common to configure a single Agent host to connect to multiple remote database instances (see [Agent installation architectures][1006] for DBM). To connect to multiple hosts, create an entry for each host in the SQL Server integration config.
-An agent with 4 CPUs and 16GB of RAM can monitor up to 30 databases with the same resources each.
+
+<div class="alert alert-info">Datadog recommends using one Agent to monitor no more than 30 database instances.<br /><br />Benchmarks show that one Agent running on a t4g.medium EC2 instance (2 CPUs and 4GB of RAM) can successfully monitor 30 RDS db.t3.medium instances (2 CPUs and 4GB of RAM).</div>
+
 ```yaml
 init_config:
 instances: