NVIDIA / NVIDIA/OSMO

Project: Backend Operators Redesign

Open
#147 0 comments 7 reactions 2 assignees View on GitHub

@ethany-nv is already working on this.

Since Dec 12, 2025.

project
Dominant language
Python
Stars
260
Forks
57
Avg merge
2d 4h
Merged PRs (30d)
69

Description

Have you read the Project Process docs?
  • Yes, I have read and understood the RFC docs
Summary

This project aims to redesign the OSMO backend operator component to address critical scaling, reliability, and performance issues.

Person in Charge (PIC)

@xutongNV

Motivation

To prepare for future growth, OSMO's backend operators require architectural enhancements to support production workloads for Kubernetes backends at large scale. The current system provides a solid foundation, but can be optimized in several key areas: system stability under sustained load, event delivery consistency, and workflow status update latency.

This redesign will proactively strengthen OSMO's ability to support production-scale deployments reliably and efficiently as customer workloads continue to grow. Rewriting the backend listener using Golang will allow us to leverage native Kubernetes Go library for more performant operations and more built-in features (such as node/pod events caching).

Problem
  1. Scaling - Single-threaded listener design limits workflow throughput
  2. Reliability - Frequently restarts, and event drops
  3. Performance - Memory leaks consume several GB per instance, and workflow status updates experience high latency
References

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.