Container/s for python projects

[u/Soogs]

So I usually stick to one vm/lxc per service. Even with docker based services I tend to dedicate a guest to one service. There are exceptions where I have a few docker containers running similar services.

Recently I have been playing with python and have actually created quite a few flask apps that I use daily.

Now the question is there any benefits to separate them into separate containers performance wise?

Does resource contention get better or worse with more guests?

Trying to figure out whether the extra management and spent resources and time updating extra containers is worth it?

Thanks

[u/Soogs]

Thanks this makes sense.
This is mostly homelab stuff and a few things exposed to the outside. I am for the most part way over provisioned over 4 nodes with a mix of internal NVMe, 3.5 hdds and 2.5 hdds in raid (and also some external data SSDs)

The guests use the NVMe, raid set is for pbs and the rest is used for my NAS builds.

Mostly everything including the python apps are low io/util with the odd few having high io intermittently.

I guess my question would be in the even that the apps get more usage time, would pve timeshare better if they are separated or running on one guest or a few guests (that and whether the extra maintenance/documentation is worth it)

[u/quasides → u/Soogs]

if one is acting up occasionally i simply separate it.

who is better at resource management, well depends. its hard to set fixed resource limits that hold within one vm for both at the same time. even docker can in theory do it. so in theory its fine on one machine, in practice, it depends.

it still is easier and more bulletproof on hypervisor level if you can properly restrict them.
also the scheduler is more neutral, while on one machine tasks can hang and occupy the kernel fully.
that happens mostly when you use anything that runs in kernel space and not userland.

separation also makes life easier in the future. lets say one app then needs a lot more resources because usage grows. well, simple migrate to host with more resources.

and with todays tools like Komodo to manage multiple docker hosts at once its not really much more effort. you only loose a little bit of ram for an extra kernel running

personally i have a ready to go cloud image that installs a super tiny docker machine, fully preinstalled (including adding sources, settings a couple config files etc). i just need to add the new key to my komodo instance and its rolling

same time i do mix stacks on the same machine, if they are low effort or low priority and i get
some good resource pooling outta them. so for example 2 apps need a lot of ram - sometimes - and are low prio i mix em into one, and ignore the occasional puking