4 ms·
This is pretty interesting from a video encoding point of view. We're currently using g2.2xlarge AWS instances which are Kepler based. All we really need from t
by wjoe 10y ago
This is pretty interesting from a video encoding point of view. We're currently using g2.2xlarge AWS instances which are Kepler based. All we really need from those instances is the GPU (more specifically, the NVENC H264 encoding chip), so other specs aren't too important.
It looks like the NV6 Azure instances use a newer Maxwell based chip, which can handle much more (concurrent, or higher bitrate/resolution) videos, compared to the 2 generation older AWS GPUs.
And the NV6 is virtually the same price as the g2.2xlarge... time to do some testing. Hopefully Amazon can catch up soon.
- dogma1138 10y agoJust for reference: K1 (AWS): 1 GPUs x 6 H.264 streams (max single stream 720p@30fps) K2 (Azure K80): 1 GPUs x 6 H.264 streams max single stream 720p@30fps) M6 (Don't know if it's used by anyone ;)): 1 GPU x 18 H.264 streams (max single stream 1080p@30fps) M60 (Azure M60): 1 GPU x 18 H.264 streams (max single stream 1080p@30fps) You can sacrifice encoder bandwidth (max streams) for higher resolutions or frame rates.
- zip1234 10y agoIs GPU better than CPU for encoding? I thought performance ended up similar. Also, are you saying that K1 AWS can reencode 6 streams at once?
- dogma1138 10y agoThe performance of the GPU is orders of magnitude better you can do multiple 1080p streams in real time with high bandwidth easily. The quality on the other hand even for the same bit rate is considerably worse than highly optimized CPU compilers as the GPU does do a lot of hacks along the way.
- valarauca1 10y agoGPU generally support more codec and faster encoding/decoding times then a CPU. But it really depends on what codec, what CPU, and what GPU.