This IS the Avid L2: Re: [Avid-L2] MacPro Mid 2010 vs mid 2012 DPX Export Performance difference?

Friday, September 6, 2019

Re: [Avid-L2] MacPro Mid 2010 vs mid 2012 DPX Export Performance difference?

I had thought they had fixed the memory leak issue. It's funny I find at home Avid link will suck up 22GB of ram creeping up the longer it runs. The same doesn't happen at work it's weird. I tried running MC 2018.12.5 but for some reason it wouldn't work with the NitrisDX circa 2009, even after I installed the included DX driver. So I couldn't go to 2018.12.5 perhaps 2018.12.7 will work with the NitrisDX. It's been a lot like herding cats of late.

What's curious is this same system has done similar shows without being so laggy. I did find an extra 8GB or ram to fill out the two open slots. Can't really tell if that's made a difference yet but I guess it can't hurt.

---In Avid-L2@yahoogroups.com, <forshurz@...> wrote :

RAM makes a difference, 2018.12.3 has a bad memory leak, and you can run apple hardware test on your work computer (extended) which will take over an hour to complete. If you really want to test, take the 64GB from your home computer and install it on your work computer and see if that's the big difference.

On Sep 6, 2019, at 4:09 PM, John Moore bigfish@... [Avid-L2] <Avid-L2@yahoogroups.com> wrote:

It feels like something has changed or gone south on my work computer.

Work computer mid 2010 MacPro upgraded to 12 Core 3.33GHz, 24GB ram, GTX-680, Mac OS 10.12.6, Avid MC 2018.12.3, NitrisDX circa 2009, 4Gig Fibre Atto card to Fibrenetix 16 drive chassis, Internal 3 way 4TB hitachi stripe raid.

Home computer mid 2012 MacPro 12core upgraded to 3.46 GHz, 64GB ram, GTX-680, Cyclone Microsystems Expansion chassis 1500 watt PS with 2 TitanX 12 GBvram GPUs, DNxIO, Mac OS 10.12.6, Avid MC 2018.12.3.

At work an hour and 10 minute DCI 4096_2160 sdr Rec 709 show took abut 8 hours to export a DPX. Now for the archival ungraded master that is unrendered it's bouncing around 12 to 14 hours and the whole system gets latent and virtually unusable. I tried reformating the Graid 20TB target drive with and the result did not improve much.

I then copied all the media for the project onto a single 4TB Hitachi Deskstar and took it home. Running the Hitachi drive as source and going to the same Graid as at work the time estimate is about 4hours and 15 minutes and the overall system is snappy as hell. I did notice on the work system that Avid memory use was at times slamming up to close to 22GB or ram and the red memory pressure was showing a lot of red. I've done this before on this system with an unrendered archival master and there was memory pressure indicated but the system didn't grind to a halt. Could ram make that much of a difference. I see at home Avid is using 36.85GB memory along with kernal task at 2.82GB, AvidOPFrameGeneratorApp 1.084GB and AVid DMFSupportSvc 866.9MB.

I would think at work with source media coming off a 16 drive san chassis connected through 4Gig fibre would supply data faster than a single spinning HD. At least the spinning HD isn't very fragmented. I'm wondering why the big difference between systems. I had asked for 64GB ram on the work system but they balked at investing in old tech. I don't know what else it could be. The only other thing is I replaced the Radeon 5770GPU in the work tower with a GTX-680 flashed for mac from another system. I've done a couple 4K shows since that swap without this issue and this timeline is simpler than most of the other shows.

I wonder if the ram is getting wonky or the fibre card or Gpu. Anybody got a suggestion on what a good hardware diagnostic to run. I might have disk warrior on the system but are there some built in utilities that might check ram etc...?

John Moore Barking Trout Productions Studio City, CA bigfish@...