<p>NVIDIA have just published <a href="https://developer.nvidia.com/video-encode-decode-gpu-support-matrix" rel="nofollow noreferrer">Video Encode and Decode GPU Support Matrix</a> that contains number of NVENC chips for Pro-level cards.</p>

CC BY-SA 3.0
2016-12-02T18:41:09.193Z
2016-12-02T18:41:09.193Z
Sergey
<p>Since you are actually more interested in performance (Frame Per Second) than in the NVENC engines count, please consider my below rounded up figures.
I've compared GTX 1060 and GTX 1080 only.</p>

<ul>
<li>H264, GTX 1080 encodes <strong>70%</strong>  faster than GTX 1060</li>
<li>HEVC, GTX 1080 encodes <strong>140%</strong> faster than GTX 1060</li>
</ul>

CC BY-SA 3.0
2016-11-04T18:28:12.673Z
1/2. Thanks for sharing publicly. By performance I didn't mean FPS of encoding of just one video but, for example, number of encoded video clips per day. To maximize the value I need to run several encoding tasks in parallel. In case of 2 engines the second parallel clip should be available like 'for free' in comparison with a card with only one engine. In my current GTX 650 setup a clip gets encoded with 68 FPS, two parallel clips with ~34 FPS which proves that the engine is in fact the only one.
Sergey
CC BY-SA 3.0
2016-11-04T18:30:48.167Z
2/2. Unfortunately I don't know if the driver can split one encoding task between several engines so we can't figure out number of engines from the numbers you provided. The source of 70/140% improvement can be in simply faster memory configuration.
Sergey
CC BY-SA 3.0
2016-11-04T14:10:28.187Z
2016-11-04T14:10:28.187Z
RawBean
<p>There is a <a href="https://developer.nvidia.com/nvenc-application-note" rel="nofollow noreferrer">NVIDIA VIDEO CODEC SDK APPLICATION NOTE - ENCODER</a> in which we can read the following:</p>

<blockquote>
  <p>While Kepler and first generation Maxwell GPUs had one NVENC engine, certain
  variants of the second generation Maxwell GPUs and Pascal Generation GPUs have two/three NVENC engines physically present on the silicon.</p>
</blockquote>

<p>So, does anyone know how to determine the number of NVENC engines in a GPU or already know the numbers? Because there is no information in NVIDIA datasheets and they are annoyingly silent in their own developer forums.</p>

CC BY-SA 3.0
2016-11-04T06:59:22.683Z
Agreed with you on "They are annoyingly silent in their own developer forums"!
RawBean
CC BY-SA 3.0
2016-11-04T07:03:06.210Z
Why do you want to know the number of NVENC engines? is it for estimating the impact on the performances ?
RawBean
CC BY-SA 3.0
2016-11-04T08:01:17.823Z
Sure. And this is also a budget question. For example, let's assume that all GeForce cards have only one engine. It means there is no sense in buying high-end card as the low-end cards contain the same chip (not sure about impact of memory performance, which are different, but I think the bottleneck is going to be in disk to memory operations not in memory to encoder).
Sergey
CC BY-SA 3.0
2016-11-04T08:10:00.537Z
In fact I has the same question than you. I bought one GTX 1060 and one GTX 1080. I benchmakred the two. It was part of my paid work so I can't share all the results publicly.
RawBean
<encoding><transcoding><nvenc>
How many NVIDIA NVENC engines a particular GPU have?
Sergey
# How many NVIDIA NVENC engines a particular GPU have?

(Asked by: username_0 on 2016-10-31)

There is a [NVIDIA VIDEO CODEC SDK APPLICATION NOTE - ENCODER](https://developer.nvidia.com/nvenc-application-note) in which we can read the following:

> While Kepler and first generation Maxwell GPUs had one NVENC engine, certain
> variants of the second generation Maxwell GPUs and Pascal Generation GPUs have two/three NVENC engines physically present on the silicon.

So, does anyone know how to determine the number of NVENC engines in a GPU or already know the numbers? Because there is no information in NVIDIA datasheets and they are annoyingly silent in their own developer forums.

**Tags:** encoding, transcoding, nvenc

> **Comments:**
> **username_1**: Agreed with you on "They are annoyingly silent in their own developer forums"!  
> **username_1**: Why do you want to know the number of NVENC engines? is it for estimating the impact on the performances ?  
> **username_0**: Sure. And this is also a budget question. For example, let's assume that all GeForce cards have only one engine. It means there is no sense in buying high-end card as the low-end cards contain the same chip (not sure about impact of memory performance, which are different, but I think the bottleneck is going to be in disk to memory operations not in memory to encoder).  
> **username_1**: In fact I has the same question than you. I bought one GTX 1060 and one GTX 1080. I benchmakred the two. It was part of my paid work so I can't share all the results publicly.  

---

## 2 answers

### Answer by username_0 on 2016-12-02. Score: 1 | Accepted answer

NVIDIA have just published [Video Encode and Decode GPU Support Matrix](https://developer.nvidia.com/video-encode-decode-gpu-support-matrix) that contains number of NVENC chips for Pro-level cards.


---

### Answer by username_1 on 2016-11-04. Score: 1

Since you are actually more interested in performance (Frame Per Second) than in the NVENC engines count, please consider my below rounded up figures.
I've compared GTX 1060 and GTX 1080 only.

* H264, GTX 1080 encodes **70%** faster than GTX 1060
* HEVC, GTX 1080 encodes **140%** faster than GTX 1060

> **Comments:**
> **username_0**: 1/2. Thanks for sharing publicly. By performance I didn't mean FPS of encoding of just one video but, for example, number of encoded video clips per day. To maximize the value I need to run several encoding tasks in parallel. In case of 2 engines the second parallel clip should be available like 'for free' in comparison with a card with only one engine. In my current GTX 650 setup a clip gets encoded with 68 FPS, two parallel clips with ~34 FPS which proves that the engine is in fact the only one.  
> **username_0**: 2/2. Unfortunately I don't know if the driver can split one encoding task between several engines so we can't figure out number of engines from the numbers you provided. The source of 70/140% improvement can be in simply faster memory configuration.  

---

