Furthermore 2021.3 version doesn't have the slow resizing behaviour.
So by narrowing down the slow resizing behaviour to specific MC version(s), we can focus on opening/closing/saving...
The question is now what is acceptable bin saving/opening/manipulating times for Viba and what is the generaly acceptable speed of these operations.
JakaBac:2018.3 has no problems resizing the project window with project on Nexis. 2018.12.15 becomes unbearably slow. Things that aggravate it is more bins (even empty ones) and wider project window. If it is resized to be narrow, then resizing it only vertically works reasonable fast (but still slower than 2018.3).
That's a different issue I haven't noticed or heard about. I just checked remotely through teamviewer on a large project from a HP z420 E5 1650 v2, quadro 2000 windows 10 20H2 nvidia driver 353.28, MC 2018.12.15, Nexis client 20.7.5, (a system on the current bottom borderline of supported configurations and performance for MC 2018.12.x, especially that grpahics card), 1Gb connected through on board nic to Nexis core 20.7.5 on a Nexis E4 120TB and the UI works, what I would call, normally. Large bins do open/close very slow but again as I'm used to.
Avid reseller ACSR at Telmaco
http://www.telmaco.gr/en/
Thanks for testing it. So no jumpyness when resizing the project window? Viba tried that on 3 machines and I tried on 2 different complete different systems and the jumpy/laggy behaviour of the project windows was consistently there with 2018.12.15, while it was OK with 2018.3 and 2021.3. And the system on which I tried 2021.3 isn't even a supported configuration (Z800 with a GeForce RTX 2080 Ti) and also this Z800 is behaving exactly the same. Fine with 2018.3 and only problematic with 2018.12.15 (but only when the project is on Nexis).
Just to be clear. I am talking only about resizing the project window. Bin saving/loading is slow, but as I said debatable on what is acceptable for a given project size :)
Hi Jakabac,
We have had some performance issues with Z8x0 with dual processors but it's some time ago and my memory isn't perfect. I do know we weren't able to solve quicktime related issues. I haven't tried that combination Z400/800 with 2018.12.15 as it is definitly out of Avid's supported configurations. But let's see.
I did a search for the Z800 configuration guide to refresh my memory on what Avid needed changed in the bios and which cards/pci-e slot configurations were supported.
http://resources.avid.com/supportfiles/attach/AVIDHPZ800ConfigguideRevB.pdf
And going throught them the first thing that triggered an 'Ah yes' was:
Embedded Broadcom BCM5764 GbE NIC Not qualified for Avid ISIS 5000 / 7000 Connectivity
We always fitted them with intel pt1000 cards for ISIS and so I would do so now for Nexis. I understand it worked under 2018.3 in your setup but as these cards can be found for little money on ebay I would get one if your Z800 isn't already equiped with one.
Furthermore, there were many Bios tweaks Avid wanted set on the Z800:
I copy pasted them. In the bios:
Select the Advanced tab - Select Processors. - Select Hyper-Threading - Default setting is Disable. Set for Enable.
Select Chipset / Memory. - Select Memory Mode Interleave - Default setting is Disable. Set to Enable
hit F10 to save the Hyper-Threading and Memory Mode Interleave settings
Select the Power tab - Select OS Power Management - Select Runtime Power Management - Default setting is Enable. Set to Disable.
Select MWAIT-Aware OS - Default setting is Enable. Change this setting from Enable to Disable.
Select Idle Power Savings - Default setting is Extended. Change this setting from Extended to Normal
Again hit F10 to save the Runtime Power Management, MWAIT-Aware OS, and Idle Power Savings
Press F10 twice to Save - Save Changes and Exit - System will Reboot
It than has the Z800 Optional system BIOS setting. I do not remember ever setting these but:
Select the Power tab - Select Hardware Power Management - Select Intel Turbo Boost Technology - Default setting is Enable set to Disable - Press F10 twice to Save - Save Changes and Exit
Finally, an RTX 2080Ti, supported or not, should work fine, but which driver to use, that I'm not sure about. If you are on Windows 10 I would start with trying the lastest as on quadro cards I have not seen issues with drivers in the 441.xx. 45x.xx and 46x.xx ranges.
With the old quadro 2000/4000 cards letting windows update choose the latest driver causes many performance issues which do resemble these UI problems you are seeing, but why only on Nexis I do not understand. But Avid is clear about that, saying that with these cards the 353.28 driver is needed and indeed MC 2018.12.15 functions normally with it. Your 2080Ti is much newer more powerful etc... but it might me you need to experiment with the driver for it.
Jeroen van Eekeres
Technical director, Broadcast support engineer, Avid ACSR.
Always have a backup of your projects....Always!!!! Yes Always!!!!
A.V.I.D....... Another Version In Development
www.mediaoffline.com
Does this site have Interplay/Production Mgt/CloudUX?
-- Bob Russo Post-Production Workflow Manager - NFL Films
Just like to bump this thread as I have been seeing reduced performance on multiple sites.
Bob, maybe you could also check something.
I just did a small test: copy the extracted media composer 2018.12.15 folder from a client to Nexis pro and Isis 5000. Unfortunately not from the same pc, I will be able to do that in a few days, but from a HP z440 with dual intel pro 1000 to Nexis pro and a HP z4 with onboard dual nic to Isis. Both on Dell n3024, n2024 switches.
Transfer time to Isis: approx 04:20
Transfer time to Nexis pro: approx 07:20
I will report more accurate numbers when doing a test from a single system to both storages.
Anyway, I have the impression for many months now that Nexis has become significantly slower saving/overwriting/deleting small files. But I never took the time to do actual comparison tests as I rarely have 2 or more Nexis systems running different version or Nexis and Isis in the same network at a customer or our reseller office but that is going to change.
Hoping you still have both Isis 7x00 and Nexis running in the same environment I would like to ask you if you can do the same test.
Furthermore I'm planing to ask Avid (support) or Ed if they can publish performance numbers for read/write/delete of groups, 10, 100 or 1000, small files of different sizes, 1Kb, 10Kb, 100Kb, 1MB, 10MB.
Thanks.
I made 6 short videos on how Media Composer behaves at opening, closing, renaming bins and resizing windows of the user interface when the project si located on Nexis and when the project is located localy. Total size of the videos is 31MB. Version of Media composer was 2021.6. But i get the same behavior with all the version 2020.x and 2019.x
You can get videos here:
open close bin - project local
open close bin - project on nexis
rename - project local
rename - project on nexis
resize - projec local
resize - project on nexis
Here is the link of the testing project:
kapa.7z
Pleas check and comment, thanx.
anyone?
Hi,
Maybe try Media Composer 2021.12.3 (or 2021.12.4)
Fixes in 2021.12.3:
Bug Number: MCCET-4478. Avid NEXIS users experienced significant performance issues when bin indexing and noticed bandwidth irregularities in the Avid NEXIS Management Console.
© Copyright 2011 Avid Technology, Inc. Terms of Use | Privacy Policy | Site Map | Find a Reseller