<p>As @Mulvya said, nearest neighbor is even faster, but will produce bad quality. Nothing resampled, so you can't get faster operation.</p>

<p>But even nearest neighbor and can cause 100% CPU load, it's depends on how much you pump information through it. If you put very large image or 1000fps, you always will get high CPU usage.</p>

<p>Only one thing you may be interested: colorspace. Try to experiment with different color spaces, like yuv420 or rgb32. Maybe some versions of scaler can be faster.</p>

CC BY-SA 3.0
2017-09-21T12:05:26.090Z
2017-09-21T12:05:26.090Z
bukkojot
<p>I'm downscaling an HD live stream to a little "thumbnail" stream, the command looks like this:</p>

<pre><code>ffmpeg -i pipe:0 -vf scale=320:240 -sws_flags fast_bilinear -an -f mpegts pipe:1
</code></pre>

<p>Now I would think <code>fast_bilinear</code> is the fastest possible scaler, but it still takes up about 60% of a single core.</p>

<p>Is there another scaler that might be better suited for downscaling? I'm not too interested in the quality.</p>

CC BY-SA 3.0
2017-09-21T11:41:11.927Z
neighbor should be faster.  But I can't test for a few days.
Gyan
CC BY-SA 3.0
2017-09-21T22:38:13.033Z
If you were wondering zscale doesn't appear to be any faster; although `filter=point` is somewhat close in speed to `flags=neighbor`.
llogan
<ffmpeg>
FFmpeg produces high system load when downscaling 1920x1080 to 320x240
Jelle De Loecker
# FFmpeg produces high system load when downscaling 1920x1080 to 320x240

(Asked by: username_0 on 2017-09-21)

I'm downscaling an HD live stream to a little "thumbnail" stream, the command looks like this:
ffmpeg -i pipe:0 -vf scale=320:240 -sws_flags fast_bilinear -an -f mpegts pipe:1

Now I would think fast_bilinear is the fastest possible scaler, but it still takes up about 60% of a single core.
Is there another scaler that might be better suited for downscaling? I'm not too interested in the quality.

**Tags:** ffmpeg

> **Comments:**
> **username_1**: neighbor should be faster.  But I can't test for a few days.  
> **username_2**: If you were wondering zscale doesn't appear to be any faster; although `filter=point` is somewhat close in speed to `flags=neighbor`.  

---

## 1 answers

### Answer by username_3 on 2017-09-21. Score: 3 | Accepted answer

As @Mulvya said, nearest neighbor is even faster, but will produce bad quality. Nothing resampled, so you can't get faster operation.

But even nearest neighbor and can cause 100% CPU load, it's depends on how much you pump information through it. If you put very large image or 1000fps, you always will get high CPU usage.

Only one thing you may be interested: colorspace. Try to experiment with different color spaces, like yuv420 or rgb32. Maybe some versions of scaler can be faster.


---

