docs/8.0/ayanova/docs/ops-config-report-rendering-max-instances.md

@@ -8,6 +8,10 @@ When AyaNova receives a report request it checks first to ensure there are not m
 
 It's important to note that this setting does not prevent AyaNova from processing a large time consuming report for any length of time necessary to complete it; this setting only takes effect when another report is requested to be rendered and there are no slots free for report rendering. For this reason, if a User has to render an unusually large report that is known to take longer than the timeout period they would be advised to render that report when no one else is requesting a report (i.e. after hours).
 
+## Performance implications
+
+Note that increasing report rendering settings too high can result in the server running out of physical memory or CPU capacity.  When increasing the limits be mindful of this potential and monitor the server carefully to ensure it's not "bottlenecking".  The reporting capacity scales directly with the amount of memory and CPU capacity available to the server.  
+
 ## Default
 
 If no override is specified AyaNova will use the following default value: