Comment to 'Slowing down video processing'
  • Hi @banister

    I would like to thank you for your research and work. It's great that someone is also looking into this. I've been thinking about this a lot lately and trying different settings and versions of ffmpeg, but unfortunately the results, such as speed and server load, weren't particularly impressive.

    I currently have the CPU limit for conversion set to 80% to keep some reserve for other tasks, but I did not limit the queue or the number of processes. Another issue is, as you mentioned, the limited configuration options on a VPS. Many administrators won’t even discuss custom setups that go beyond the standard service.

    I came to the conclusion that running a live website with videos and multiple users is simply not feasible on a VPS — or at least not financially worthwhile. VPS is great for small projects, testing, and development, but not sufficient for large-scale production. There should be at least two servers — one for the main website and another for backups.

    If you have the knowledge, you can even use a third server dedicated to remote video processing. It’s a lot of work and money, but in the long run it saves costs, since owning your own storage is always better.

    Yes, it can be expanded using AWS or similar services, but then you’re handing over your data to someone else — which, in my case, I refuse to do.

    We all know times are tough, and user data is the most important thing you must protect. I'm not encouraging anyone to do anything and I don't mean it badly, I just came to this realization through time and suffering with VPS.