Serious Lag times in Multiconsole

Hi Anna-Lena,

Would you please gather the following and please upload the files here.

• Logs from all consoles/Clients
• Latest copy of the showfile
• Details about the Nomad Client machine - make/model/OS/Processor/RAM
• A description/sketch of the network topology with make and models of the switches
• Configuration files of the switches as well if you have them

Have you tried without the Client connected?

Thanks, Seth

Uploaded! The client Nomad is running on a Windows Surface 3 with 2.7GHz i5 and 4GB Ram with a universal fader wing. 

This began happening before we started using the Nomad, but has gotten worse since.

Thank you for all the data Anna-Lenna we are working through the logs and will be back in touch soon.

Anna-Lenna,

From the logs and reproducing it here at ETC, we see the hangs (lags) occurring after leaving Patch the first time after each restart of Eos.  This matching an existing known issue [EOS-51663].

A few things to limit this:

• As you mentioned Deep Clearing all machines will help get you to a clean state. 
• Enter Patch early in your day, then exit (get the hang over early and not in the heat of the moment)
• Then close all instances of Patch - leaving Patch open on large showfiles can affect performance
• Snapshot 3:
  • Remove Patch
  • Evaluate the number of Magic Sheets and sACN Output Viewer tabs that are open as the quantity is affected available resources

Looking a bit more at your Surface's logs, it is probably not going to meet the minimum requirements for running Augment3d (ETCnomad & ETCnomad Puck : Hardware Specifications).  I would recommend disabling Augment3d on that device: Running Augment3d

You also have many Unpatched channels.  Any data stored to those channels contributes to CPU overhead, even though they're not outputting anywhere (the system has to be ready at a moment's notice to output those when you attach an address to them).  Deleting channels that you'll never use the same way again will help reduce the overhead.  You can find these channels in Patch using {Query} > {Unpatched}:

Do be careful, because you could potentially delete channels that you're using for By-Type Palettes.

Looking a bit more at your Surface's logs, it is probably not going to meet the minimum requirements for running Augment3d (ETCnomad & ETCnomad Puck : Hardware Specifications).  I would recommend disabling Augment3d on that device: Running Augment3d

You also have many Unpatched channels.  Any data stored to those channels contributes to CPU overhead, even though they're not outputting anywhere (the system has to be ready at a moment's notice to output those when you attach an address to them).  Deleting channels that you'll never use the same way again will help reduce the overhead.  You can find these channels in Patch using {Query} > {Unpatched}:

Do be careful, because you could potentially delete channels that you're using for By-Type Palettes.

Thanks for this! Unfortunately there is much I can't delete, but I will do what I can, as well as disabling augment3d.