Media & Entertainment and HPC Modes
Object Mount for Linux includes an environment variable called CUNO_PROFILE that modifies internal application behavior for different types of workloads.
This setting only applies to Object Mount on Linux and helps Object Mount optimize itself for Media & Entertainment (M&E) and High-Performance Computing (HPC) workflows:
| CUNO Profile Setting | Workflow |
|---|---|
CUNO_PROFILE=M&E | Media & Entertainment workflows |
CUNO_PROFILE=hpc | High-Performance Computing environments |
Understanding the behavior of each mode is important.
Setting the wrong mode can negatively impact expected performance, especially in large-scale automated environments.
Purpose of CUNO_PROFILE
The CUNO_PROFILE variable adjusts how Object Mount behaves internally, including:
- How aggressively metadata is cached
- Which filesystem features are exposed
- Logging, debugging, and memory handling profiles
- Compatibility expectations with the Linux UserLAnd and toolchain tools
Default Profile Mode
If unset, the default is for Media & Entertainment workflows: CUNO_PROFILE=M&E.
Media & Entertainment Mode is well-suited to desktop users, editors, and creative professionals using Object Mount interactively, but less appropriate for headless systems or scripted automations.
Choosing the Right Profile
Before installing or configuring Object Mount for Linux, consider the following questions:
Is the user working interactively? Or via headless automation?
M&EMode is tuned for interactive, graphical workflowshpcMode is preferred for background tasks, CLI tools, and scripts
Will the mount be used by creative software applications?
- If using Apps such as Avid Media Composer, DaVinci Resolve, Apple Final Cut Pro, Adobe Premiere Pro, etc.:
- Set:
CUNO_PROFILE=M&E
- Set:
- If running scripted automation tools, media transformation pipelines, background archive/backup jobs, etc.:
- Set:
CUNO_PROFILE=hpc
- Set:
- If using Apps such as Avid Media Composer, DaVinci Resolve, Apple Final Cut Pro, Adobe Premiere Pro, etc.:
Is the system a personal workstation? Or shared server node?
- Personal Workstation — Set:
CUNO_PROFILE=M&E - Server node / render farm — Set:
CUNO_PROFILE=hpc
- Personal Workstation — Set:
Is the mount expected to be long-lived and static? Or frequently toggled?
- Session-based, user-initiated mounts — Set:
CUNO_PROFILE=M&E - Long-lived, persistent mounts — Set:
CUNO_PROFILE=hpc
- Session-based, user-initiated mounts — Set:
Will users be working via GUI, or purely via CLI/API?
- GUI or desktop usage — Set:
CUNO_PROFILE=M&E - CLI tools, automation, batch jobs — Set:
CUNO_PROFILE=hpc
- GUI or desktop usage — Set:
Which is more important: latency or throughput?
- Low-latency I/O, fast response time “desktop feel” — Set:
CUNO_PROFILE=M&E - Bulk, high-throughput, background tasks (e.g.: rendering, transcoding) — Set:
CUNO_PROFILE=hpc
- Low-latency I/O, fast response time “desktop feel” — Set:
Setting the Profile
To explicitly set the profile, define the environment variable before launching Object Mount.
For example:
For permanent use, add the environment variable setting to:
- Your shell profile (
~/.bashrc,~/.zshrc) - A systemd service or login script
- Docker or container entrypoints (if applicable)
Table: Use Case Quick Reference
| Use Case | Recommended Profile |
|---|---|
| Media & Entertainment Workflows: | |
| • Desktop video editing | M&E |
| • Interactive audio work | M&E |
| • Local workstation media previews | M&E |
| High-Performance Computing Environments: | |
| • Automated ingest pipelines | hpc |
| • Render farm nodes | hpc |
| • Remote headless access | hpc |