With ENTESB-16898 performance of Fuse Console on OpenShift is improved and now it has a capability to even view an app with 500+ Camel routes in a lab environment. (Before the fix, it was not possible to view even less than 200 routes.) However, due to bottlenecks in several places of the default resource settings, it requires performance tuning on the default settings to unlock the capability.

Please document the following instructions.

Performance tuning

Here are the three steps on how to performance tune Fuse Console on OpenShift for viewing applications with a large number of MBeans:
https://issues.redhat.com/browse/ENTESB-16898?focusedCommentId=20236932&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-20236932

1. Increase the memory limit for the application: e.g. 256Mi -> 512Mi. This is necessary for the app not to crash with OOM at the app side even before reaching Fuse Console. For a Fuse quickstart, you can increase the memory limit by modifying its src/main/jkube/deployment.yml like this:

   spec:
     template:
       spec:
         containers:
           - 
             resources:
               [...]
               limits:
                 cpu: "1.0"
                 memory: 512Mi

1. Make sure Fuse Console Deployment or DeploymentConfig has an enough memory limit. If it's not enough, increase the limit, e.g. 200Mi -> 512Mi.
2. Finally, apply the solution from FUSEDOC-4692 if you see the "too big subrequest response while sending to client" error in nginx log. For example, in a lab envirnoment this was enough to render 500 routes:

           - name: NGINX_SUBREQUEST_OUTPUT_BUFFER_SIZE
             value: 100m