Mark, to put it in perspective... I've been managing an Enterprise Project Management app for several years now that is currently ~2.9GB in size with ~1300 registered users. This app easily swells over the allotted RAM limit. Upon exceeding the limit, an application will reboot without notice. We don't have any monitoring abilities to understand what our current RAM footprint is at a given time... so hitting a limit like this in business hours can easily cause a 30+ minute outage for the app to reboot and for queuing to come back under control with reasonable responsiveness. We've been partnering with QB staff and our QSP for the past 9 months (including Harrison) to combat the issue with mixed results. Though we've optimized reporting/dashboards/limited-personal reports for quicker response times... our RAM consumption issue still persists.
I do believe that if we could create an hour of "quiet" time for the app to go-to-sleep / unload itself at night, the issues would not occur anymore. The app never puts itself to bed currently. This a very difficult item to control with the vast user base, nightly processes for our company, and nightly processes configured within Automations themselves. We need 30-minutes of zero utilization for the app to unload itself.
I'm confident we'll get this figured out, but our users are definitely frustrated.