ffmpeg dedicated server VS cloud server?

Question

fmpeg

I need to convert a huge amount of videos through FFMPEG. When converting on one of the dedicated servers, it starts to hang terribly (which is logical in principle).
To solve the problem, I took Cloud Scale Server (Clodo) with maximum settings (14 Core, 16GB RAM). In terms of performance, of course, it is several times stronger than my Dedicated server. But that wasn't the case...
The same file:
Dedicated fps=400-500
Cloud fps=200-220.

What could be the problem?
The first thing that came to mind was the OS. The first is Centos, on Cloud Debian.
The second is the quality of the Cloud server… Is it really that bad?

UPD:The problem is most likely not in Clodo, but in processors. Now we checked fps on a 2xXeon E5645 (12x2.4GHz) and fps is similarly 200 ... Only 4 cores are used. On my first server, Xeon E3-1230 3.30GHz gives out 400-500 since it's 3.30GHz.

Answer 1

Well, for starters, I will “please” you with 14 “cores” for Klodo, these are 7 cores from 2x 4-core Intel Xeon E5520 (which, let’s say, is obsolete in itself), with hypertrading enabled.
With the same selector, you will get 8 rather than 7 cores and are much cheaper (90 kopecks / hour per core, drinking 1.5 rubles / hour for 0.5 cores).

Answer 2

Cloud scale is almost certainly not a real server, but a virtual one, and physically you share this server with someone else (this is exactly why you get the ability to scale). it's still a miracle that you only got a 2x performance hit. And if you look at the money, it’s generally terrible :) these clouds are really sad, they are useful only for short periods of time.
A dedicated server, by definition, will work faster than a virtual one (at least not slower), the exceptions are cached data from the launch of neighboring / previous instances, which in practice only happen when the virtual machine itself is launched (if these virtual machines were created by snapshot from one).
ps I also achieved amazing disk write performance inside the virtual machine, if I forced write back (or whatever, they are called differently in different virtual machines / storages), but at the expense of a significant decrease in reliability, i.e. if something happens to the hardware, there will be a pipe with the data, so serious providers do not touch these options.

Answer 3

In principle, if it is speed that is important to you, then according to cloud ideology - create 1 server for each video (Well, or 10 videos / server) and convert in this way. The cloud scales here almost to infinity. The cost of one such server in the off state and only with ipv6 and a minimum disk (4GB + 1GB swap) will be only 16.2 rubles / month, if more space is needed, it will increase proportionally. The point of the cloud is not that there is one super-powerful server, the point is that you can create many machines on different servers to process data in parallel and pay only for use.

Answer 4

When converting on one of the dedicated servers, it starts to hang terribly

And what did it get into? Of course, I'm not a Linux expert, but it seems like you can tweak nice there - and then ffmpeg will not bother anyone - if it's the CPU ...

Answer 5

Go to the selector and try it.

Answer 6

set the number of threads when converting, so as not to clog all the processor time.