Jobs with large state take a long time to show in UI

[nyurik]

If a job has a very large array (a few MBs) of some internal state, that whole value is downloaded to the browser in the UI. I think that some values, e.g. ones that begin with '_', should not be downloaded, allowing much more efficient job management.

[behrad]

I think we should lazy load job.data & job.results

[nyurik]

I suspect there is a bit more to it - even though the queue is created with jobEvents=false, when I view the jobs via UI, I suspect that it re-subscribes to all the job, or keeps re-downloading them on each refresh, thus causing out of memory problems.

[alanclarke]

+1

[guillermodoghel]

+1