12/24/2022 0 Comments Intel quicksync and blender![]() ![]() ![]() The Intel i9-9980XE stock CPU completed the same render in 22% less time than the 9900K with IGP acceleration, with the $3000 Intel Xeon 3175X completing its render in 12 minutes, reducing the time required from the $2000 9980XE by 27%. Note that IGP acceleration helps primarily with our charted reviews, but doesn’t do as much for heavy a-roll and b-roll videos like this one. The Intel i9-9900K stock CPU completed our render in 24 minutes, or 21 minutes when using QuickSync, which isn’t available on the HEDT CPUs. Premiere likes cores more than Photoshop, but is still heavily frequency dependent. ![]() Adobe software in general, including Photoshop, really likes frequency. This workload represents what we go through every day when rendering reviews. Our years of experience with Premiere have taught us that our charts sections are heavily reliant upon the GPU, so those have been removed from CPU tests, and that working with high bitrate, high resolution files will stress the CPU heavily. H.264 is used, as YouTube still isn’t ready for primetime on H.265. We firmly believe this is a real-world scenario, knowing most of the tech YouTubers you all watch, and find this a representative workload for content creators. The render is CUDA-accelerated, but the majority of the work still bottlenecks on the CPU. We’ll play some of that file back now so you can get an idea for what’s being rendered. The video is an 11-minute truncated GPU review, using only a-roll and b-roll clips at 4K60 and rendered at 45Mbps. Our first test uses Adobe Premiere to encode a real GN clip. Note: 3175X system used 6 slots populated with 3200MHz Vengeance LPX.All quad-channel HEDT platforms: 4x 8GB 3200MHz Corsair Vengeance LPX 16-18-18-36 DDR4.(Exception: Z97X uses HyperX Savage 2133MHz DDR3).All desktop platforms: 2x 8GB 3200MHz Corsair Vengeance LPX 16-18-18-36 DDR4.Motherboards used for testing are as follows: Tested CPUs primarily include the below list: A better cooler would be strongly advised, as we were operating at an intolerable 70dBA (at 20”) with the Asetek cooler, which is simply unsustainable beyond some benchmarking.īeyond this, all overclocking is the same as Skylake-X, seeing as the part is Skylake-X architecture, ultimately. Using the ASUS Dominus BIOS, we increased maximum core temperature to 90 degrees, allowing the 4.5GHz OC to run just below throttle point. The biggest limiter to performance was thermals, as stock TjMax is 85 degrees Celsius and the stock interface is paste (between the die and IHS). We can push the clocks higher in non-AVX or game testing, where CPU load is lessened, but that doesn’t quite fit within our requirements. Our overclock requirement for reviews is that the CPU must pass all tests, including our Blender AVX workloads, in order for the OC to be considered valid for review. We ended up stuck at around 4.5GHz / 1.15V (1.17V for Premiere) for our testing, with a quick mesh of 30x. The cooler is weak when compared to the EK solution, primarily thanks to its usual Gen5/Gen6 pump block design coupled with an extended coldplate, but still gets the job done. We chose to test with the Asetek cooler shipped by Intel at first, as this is likely to be included in SI configurations. The Intel Xeon W-3175X is a 28-core CPU, and that means it’s going to run unabashedly hot when overclocking. So you can see it is saying this video encoded with the nVidia NVEnc is CAVLC whereas the same video encoded with x265 comes out with CABAC.Most of our overclocking detail will be revealed in our OC livestream tonight (6PM EST, 1/30/19), but we can also speak to the overclocking experience here. Stream Type : Main Profile Level 5.2(156) Tier High Video Format : YUV420 Luma bit: 8 Chroma bit: 8 I have managed to get it encoded, I do not know why it was not working when I tried previously because I did not alter anything when I re-tried and it did successfully encode the video. ![]() I used the same avisynth script which worked fine with MeGUI but Hybrid kept failing to encoder it and I have not yet managed to sort that out. Next I ran into a problem encoding the small video that I used with the x265 encoder with MeGUI. An install with the latest version which I had not got around to install before then fix that, at least it now runs & starts up. I ran into some problems which has prevented me from adding to this thread. Can you give an example of the nvenc output with CAVLC? ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |