Roadmap for improvements for Multi-process cook task load balancing?

Hi,

I was wondering if there are any plans to improve the way multiprocess cook works in the near future? Two specific parts are

  1. how package cooking tasks are load-balanced between workers? Specifically, it looks like FCookGraphLoadBalancer uses hard-coded save and load costs that aren’t representative for the packages. I haven’t dug through all of the code yet, but I’m not sure if it also tries to calculate or proxy a cooking cost for the asset to use as part of load balancing either.
  2. supporting remote cook worker machines/processes? possibly using something like Incredibuild or HordeAgents, so these multiprocess cooks could reuse existing build/farm infra? i saw this post discussing some of these points, but it’s a year old:
    https://epicprosupport.epicgames.com/s/question/0D5QP000006EDeg0AG/multiprocess-cook-force-a-uobject-to-use-a-specific-worker

Thank you!