How can I proactively identify content that overloads runtime servers?

Hi Pyramid Team,

I am looking for recommendations on how to proactively identify Pyramid content that may overload runtime servers.

I had a case where opening a specific content item caused very high memory usage on runtime servers. The runtime machine became almost unresponsive because of memory exhaustion, and requests routed to that runtime started hanging.

My question is about prevention. I want to understand how an administrator can find this kind of risky or inefficient self-service content before it affects the environment.

Questions:

1. Are there built-in admin tools, logs, audit data, repository queries, or monitoring views that show which content items consume the most memory on runtime servers?

2. Is there a way to identify reports, dashboards, or models that create very large intermediate result sets or expensive runtime queries?

3. After a runtime overload event, is there a recommended way to identify which content item caused the memory spike?

4. Are there recommended limits, alerts, or isolation settings that can prevent a single heavy content item from overloading runtime servers?

5. What is the recommended process for reviewing and optimizing this type of content in self-service environments?

The goal is to detect and review this type of content in advance, before it overloads runtime servers.

Pyramid version: 2024.03.002

Thanks