Update max-connections tuning recommendation (#2717)

Co-authored-by: Karl Eichwalder <[email protected]>

CHANGELOG.md

@@ -1,3 +1,4 @@
+- Updated max-connections tuning recommendation in Large Deployment Guide
 - Added troubleshooting instructions for setting up in public cloud
   (BYOS) to Administration Guide
 - Added detailed information about the messages produced by subscription

modules/specialized-guides/pages/large-deployments/tuning.adoc

@@ -503,7 +503,7 @@ This section contains information about the available parameters.
                          However, each connection consumes resources, in particular xref:work-mem[`work_mem`] megabytes per sort operation per connection.
 | Tune when            | xref:hibernate-c3p0-max-size[`hibernate.c3p0.max_size`] changes significantly, as that parameter determines the maximum number of connections available to Tomcat and Taskomatic
 | Value default        | 400
-| Value recommendation | 2 * xref:hibernate-c3p0-max-size[hibernate.c3p0.max_size] + apache xref:server-limit[`MaxClients`] + 70, if less than 1000
+| Value recommendation | Depends on other settings, use [command]``/usr/lib/susemanager/bin/susemanager-connection-check`` to obtain a recommendation.
 | Location             | [path]``/var/lib/pgsql/data/postgresql.conf``
 | Example              | `max_connections = 250`
 | After changing       | Check xref:memory-usage[memory usage].