Peformance Isolation for Inference Processes in Edge GPU Systems

This paper evaluates NVIDIA's GPU isolation mechanisms (MPS, MIG, and Green Contexts) on A100 and Jetson Orin platforms to determine their effectiveness in ensuring predictable inference times for safety-critical edge applications, finding that while MIG offers high isolation, Green Contexts provide a promising low-overhead alternative for edge devices despite lacking memory isolation.

Original authors: Juan José Martín, José Flich, Carles Hernández

Published 2026-01-28
📖 5 min read🧠 Deep dive

Original authors: Juan José Martín, José Flich, Carles Hernández

Original paper licensed under CC BY 4.0 (http://creativecommons.org/licenses/by/4.0/). This is an AI-generated explanation of the paper below. It is not written or endorsed by the authors. For technical accuracy, refer to the original paper. Read full disclaimer

Imagine you have a super-fast, high-powered chef (the GPU) in a kitchen. This chef is incredibly talented at cooking complex dishes (running Deep Learning models) to help make important decisions, like helping a self-driving car see a pedestrian or a medical device diagnose an illness.

In the world of "safety-critical" applications, it's not enough for the chef to just be good at cooking; they also need to be predictable. If the chef takes 2 seconds to chop an onion today, they must take exactly 2 seconds tomorrow. If they get distracted by another order and take 5 seconds, that could be dangerous.

The problem arises when you try to make the chef cook multiple dishes at the same time to save money and space. If two orders come in, they might fight over the same cutting board, the same stove, or the chef's attention, causing delays.

This paper tests three different ways to organize this kitchen so that every dish gets cooked on time, even when the chef is busy with multiple orders. They tested these methods on two types of kitchens: a massive, industrial kitchen (NVIDIA A100) and a compact, energy-efficient food truck (Jetson Orin).

Here are the three "kitchen management strategies" they tested:

1. MPS (Multi-Process Service): The "Shared Apron" Approach

  • The Analogy: Imagine the chef wears a special apron that allows them to switch between two recipes instantly without taking off their hat or washing their hands. It's a software trick to make the chef feel like they are doing two things at once with very little "switching cost."
  • The Result: This works well for making the kitchen faster overall. However, it's like two people sharing a single pair of scissors. If one person grabs them, the other has to wait. It doesn't guarantee that the second person will finish on time if the first person gets too busy. It's good for general speed, but not safe enough for critical emergencies.

2. MIG (Multi-Instance GPU): The "Walled Garden" Approach

  • The Analogy: Imagine the chef's kitchen is physically divided by walls into two separate rooms. Each room has its own stove, its own cutting board, and its own chef (or a dedicated portion of the main chef's time). One room cannot touch the other's ingredients or tools.
  • The Result: This is the gold standard for safety. Because the rooms are physically separated, if the chef in Room A gets overwhelmed, the chef in Room B doesn't care. They get their own guaranteed time and space.
  • The Catch: The walls are rigid. Once you build the wall, you can't easily move it. If one room needs more space and the other needs less, you can't just shift the wall; you have to rebuild it. Also, this "wall" technology is only available in the big industrial kitchens (A100), not the small food trucks.

3. Green Contexts (GC): The "Time-Boxed" Approach

  • The Analogy: This is a newer, clever software trick for the small food trucks. Instead of building walls, the manager gives the chef a specific list of "tools" (specific parts of the stove) that they are only allowed to use for a specific dish. The chef knows, "I can only use burners 1 and 2 for this order."
  • The Result: This is very flexible and lightweight. It doesn't slow the chef down much.
    • On the Big Kitchen (A100): It works great, acting like a soft version of the walled garden.
    • On the Food Truck (Jetson Orin Nano): It hit a snag. Because the food truck is small and has a strict power limit (like a small generator), when the chef tried to cook two dishes at once, the whole truck started to "overheat" and the power generator slowed down. Even though the chef was told to only use specific burners, the whole truck slowed down because it was running out of power.
    • The Fix: When they tested this on a slightly bigger food truck (Jetson Orin AGX) with a stronger generator, the "Time-Boxed" approach worked perfectly, isolating the dishes just as well as the walled garden.

The Big Takeaways

  1. Big Models vs. Small Models: Some dishes (large AI models) are so heavy that they use the whole stove anyway. They are hard to slow down. Other dishes (small models) are light and rely heavily on the speed of the delivery service (memory). If the delivery is slow, these small dishes get delayed easily.
  2. The Power Problem: On small, portable devices, power is the biggest enemy. If you try to run two tasks at once, the device might run out of juice, causing the whole system to slow down, breaking the "isolation" promise.
  3. The Future: The paper suggests that while "Walled Gardens" (MIG) are the safest, they are too rigid. The "Time-Boxed" approach (Green Contexts) is the future for small devices, but we need to invent a way to give them their own "memory" (like a private pantry) so they don't fight over the delivery service.

In short: If you need absolute safety and have a big machine, build walls (MIG). If you are on a small, battery-powered device, you can use the "Time-Boxed" method (Green Contexts), but you have to be careful not to ask the device to do too much at once, or it will run out of power and slow everything down.

Drowning in papers in your field?

Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.

Try Digest →