Dozens of encoding process for a single video?

[AnthonyTorreso]

I must say I love love love this piece of software, truly an amazing feet. With this I just noticed that when I encode a mp4 it spawns off dozens of processes. Is this normal or did I misconfigure something?

Thank you,
Anthony

[working-name]

It's normal, part of chunking and encoding setup. Essentially mediacms spawns as many "encoders" as it is allowed by the hardware, to encode small chunks of the whole video across multiple CPU cores to speed up the process (parallel versus sequential).

The green items in htop are "userland threads", aka threads within the same process that allows parallel tasks to be completed. This happens at the process level, not the kernel level like a regular process, hence the "userland" part. What this means is that you cannot count the green highlighted processes as another process.

WARNING: if your server does not have appropriate resources (swap file > RAM size, no other crazy load), mediacms in its current vanilla docker implementation will kill your server. It will use up every ounce of CPU/RAM/swap you have if you do not set up deploy: limits in the docker-compose.yml file. The containers I notice do encoding are celery_beat, celery_worker, and web For example:

    deploy:
      resources:
        limits:
          cpus: "4"
          memory: "4g"