|
Quote
Congrats, you just found a bottle neck. I don't think it's bandwidth related, but more of latencies.
Yeah I am becoming a believer that how stuff is moving around is the limiting factor. - not so much the speed of any part
|
|
Quote
Yeah, memory bandwidth helps, but more importanly the system's memory acccess latency goes down with the number of channels used to access it.
.
I have not had a chance to try using all 8 memory channels yet but I did get and interesting surprise when I added one of the new StarTech dual NVMe x8 cards. The rederening time of my test project dropped 25% and I noticed the GPU usgae went from 41% to 53%.
This is using two Samsung Evo 970 Plus NVMe SSD's. They were previously each mounted on the usual x4 adapter card. The only change in the system was removing them from the two x4 cards and moving them to the new single StarTech x8 card...
|
|
Quote
I have 64GB in my system now, not because I needed that much memory, but because I wanted 4+4 channels (each CPU has a Quad controller) to access my DDR3 memory (T7610 here, with two E5-2667 V2). So I have installed 8 sticks of 8 MB in my machine (of 16 slots total), 4 sticks for each CPU (to use their Quad channels)
Thanks I would have never thought of that. I had four 16GB RDIMMs sitting on the shelf which is why I ended up with 128GB total - I don't need that much memory. I shall experiment - I will borrow some memory from another workstation and play around...
|
|
Quote
Like I said above, the PD hits other bottlenecks, to me looks like latency.
I agree which is why I was little surprised there was a 15% increase by adding the second CPU. Given with one CPU it wasn't using a 1/3 of the CPU. The only thing I could think of is the second CPU has it's own access to a seprate pool of memory which means memory bandwidth went up...
|
|
Quote
Check pref, you are probably doing CPU decoding while hardware GPU encoding. Stats would have indicated too if the case.
Jeff
2 screenshots attached
|
|
Quote
Open task manager, and then hit "Performance" tab. You can see the CPU usage and GPU usage during editing.
If you are doing only encoding, the CPU will not be used that much. If you apply any effects (LUT for example), it might change things.
33% usage CPU on the two XEONs - 66% CPU usage on the single XEON
37% GPU usage on the two XEON's - 41% GPU usage on the single XEON (peek in bioth cases)
somehow I knew you would ask for the above
and...
6% memory usage on the two XEONs (128GB) - 15% memory usage on the single XEON
|
|
Quote
I
Using a complex project I had (4 1920x1080 40bps input streams with key frames on output) the following results happen...
Production time on a T3420 without hardware encoding 46:23 and with it 33:43
Production time on a T7910 without hardware encoding 45:10 and with it 31:32
I added a second CPU to the T7910 workstation. WIth hardware encoding the encoding time was 27:24. I ran the test several times to make sure. Within a second the same each time. Not sure why
Differences in hardware...
2 vs 1 Xeon E5-2667 V3 3.2 GHz
16 Cores (32 Logical Processors) vs 8 Cores (16 Logical Processors)
.5MB vs 1 MB L1 Cache
4 MB vs 2 MB L2 Cache
40 MB vs 20 MB L3 Cache
6 vs 2 Memory Channels (added four 16GB RDIMMs to the existing two 32GB RDIMMs)
|
|
Quote
Thanks for the testing.
> 1920 x 1040. (Is that a European standard
Nope - it is a typo ;
|
|
>
Quote
> The use of SSD for video editing is a complete waste of money, the encoding speed is way below what a modern HHD can do, even at 4K.Check with Windows "Resource Monitor" and you'll see the HDD usage.
On that we will disagree - I have seen up to a 5% different between sourcing from a HDD vs a SDD. However for SATA SSD vs PCIe SSD there was no difference. While you are using internal RAID I am not. Given the cost of Samsung 970 Pro PCIe NVM disks are south of $100 now the cost isn't high anymore. The only thing I use the SDD's is the current project I am working. I archive 2 copies of any finished project on HDD's using a RocketStor 3122B
I did a lot of testing of various hardware combinations
|
|
I was able to run tests using what may be the perfect environment to answer this question...
Dell Precision T3420 Intel Xeon E3-1245 V5 3.5ghz (4 Core 8 Logical Processors) - 64GB - dual PCIe M2 Drives - Integrated Intel Graphics
Dell Precision T7910 Xeon E5-2667 V3 3.2GHz (8 Core 16 Logical Processors) - 64GB - dual PCIe M2 Drives - GeFore RTX 2060 Graphics
In each above PD365 wasn't going to be limited by CPU speed or Cores (nowhere near 100% CPU usage). Nor was it going to be limited by disk speed (PCIe M2 Drives are the fastest you can get for a workstation)
That means there wouldn't be another limit impacting performance when I tested with and without hardware encoding.
Using a complex project I had (4 1920x1080 40bps input streams with key frames on output) the following results happen...
Production time on a T3420 without hardware encoding 46:23 and with it 33:43
Production time on a T7910 without hardware encoding 45:10 and with it 31:32
FYI - The output file was 36:52 in length which in best case it was producing about 1 minute of video each for every 51 seconds of production time
In both cases the source files were NOT on the system disk because that will slow you down about 1/2 of a percent
So when hardware encoding is the only performance factor was in these test it takes about 1.5 times longer to produce a video without using hardware encoding
Now don't assume that is a universal rule i.e. you pop in a graphics card that can do hardware encoding and your production time will be 2/3's for what it was. If your CPU speed, number of cores, or disk speed are issues they like will wash out some of that performance improvement...
|
|
I deleted all version of PD off my workstation - rebooted - and purchased/installed PD365 (AKA PD1. The hardware encoder now works.
I didn't try it but in the article below it suggested there is patch for PD17 than will allow it to work with the current GeForce driver.
https://www.cyberlink.com/support/faq-content.do?id=23917
p.s. I was alread toying with the idea of going to PD365 i.e. I didn't do it just to fix this problem
FYI I added the comment about the RTX 2060 driver to the support ticket
|
|
I have a Dell T7910 workstation (E5-2667 V3) and I thinking about upgrading it to a dual processor workstation. The question here is NOT about the value of going from one E5-2667 to dual E5-2667.
However it did get me wondering about what would happen if I put another GeForce RTX 2060 card in my system. Would PD18 make any use of it during rendering? In other words does PD18 use a second GPU if it finds it?
|
|
FYI...
Reply from CyberLink Customer Support2020/03/12 14:27
Hi Jeff,
Thank you for contacting CyberLink Technical Support.
We understand that you are unable to enable the hardware video encoder on your PowerDirector 365. We are more than willing to assist you with your concern.
With reference to your query, please be advised that a new hardware video encoding mechanism was implemented in NVIDIA VGA driver version v416.xx.
Due to stability concerns and technical limitations, the architecture of earlier software versions is not compatible with the new hardware video encoding mechanism. As the result, not all CyberLink software supports the new NVIDIA hardware video encoding mechanism.
For your CyberLink PowerDirector 365, it is suggested that you install NVIDIA VGA driver version v411.XX or below if you need to use NVIDIA hardware video encoding technology to produce your video.
NVIDIA driver download website: https://www.nvidia.com/en-us/
For more details you may also visit the link below for your reference.
https://www.cyberlink.com/support/product-faq-content.do?id=23917
If the concern still persists, please provide the following information below for us to better assist you.
Kindly provide the updated DxDiag after reinstallation of the said driver.
Full Screenshot of error message, if any. To take a full screenshot
1. Press PrtScrn on the upper right side of the keyboard.
2. Open Windows Paint (press Windows button, type the word Paint then click on the result to open the program).
3. Paste the screenshot (press Ctrl+V), then save the file (in .jpg format).
Screenshot of the Product Version or SR Number.
1. Launch PowerDirector 365.
2. Click Logo of the software or the name of the software.
3. Take a screenshot of the window showing the software information.
Full screenshot of the produce tab showing that the hardware video encoder is greyed out.
Please feel free to contact us back for further clarification or assistance related to CyberLink Products. Use the link below to get back to us:
https://membership.cyberlink.com/support/service/technical-support.do
Thanks and Regards,
Alvin
CyberLink Technical Support
|
|
Ticket Number
Cyberlink] Online Customer Support (QuestionID = CS002124167)
|
|
Thanks for your help and I will submit support request here.
|
|
Same problem. Here is what I did
1) Uninstalled anything "NVIDIA" from the system
2) Uninstalled PD including remove personal settings
3) Rebooted
4) Run the Dell updates which included a couple BIOS updates
5) Rebooted
6) Installed the NVIDIA Studio stuff using the link you provided and did "drivers only" with custom -> clean install
7) Rebooted
Installed PD17 and answered to the question about wanting to optimize
9) Tried Project that worked before on another system (with Intel Integrated Graphics - could not check the hardware optimize on produce
10) Tried a fresh small video that I just did a few edits to - could not check the hardware optimize on produce
New DxDiag file attached
|
|
DxDiag output attached - that looks much easier to read
|
|
I think the attached is the registry key in that posting you referenced
Sorry about not pulling the correct data the first time
DxDiag in the next posting
|
|
Attached are system information files (in Zip FIles). Need anything else?
BTW - Not having this issue on the Dell T3420 I am upgrading from - The T3420 has intergrated Intel graphics and the T7910 with the RTX 2060 does not have integrated graphics...
|
|
The Dell 7910 workstation is being repurposed and will be used for PowerDIrector ONLY. I has a 100% new Windows 10 Pro install and a fresh PD17 install - never crashed. I installed the Studio version of the NVIDIA drivers.
See files attached in this message and next
|