Best Practice for Isolating Self-Service Workloads in a Single Installation

Hello PA-Team,

I'm looking for advice on a common enterprise challenge: how to ensure the stability of my critical corporate reports in a mixed-use environment where self-service users are also active.

The Problem:
In my single Pyramid installation, I have both corporate reports (running on a dedicated In-Memory server) and self-service models. I've experienced situations where a heavy query from a self-service user overloads the runtime servers, causing the entire installation to become unstable. This directly impacts my business-critical corporate reporting.

My Goal:
I want to isolate the workloads to prevent self-service activity from affecting corporate report availability, within a single Pyramid installation.

I know that setting up separate Pyramid instances is one solution, but for operational reasons, I am looking for ways to manage this within one environment.

The Question:
What are the recommended best practices or architectural patterns within Pyramid to achieve this kind of workload isolation?

For example, is there any way to influence the router's behavior to dedicate specific runtime or task servers to specific data sources (like a particular In-Memory server)? Or are there other methods for resource governance that I might be missing?

Any insights or alternative solutions would be greatly appreciated.

Thanks