You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Tracking wallclock and cpu time used in inference is challenging in the distributed inference pipelines we're running, as they are often interrupted with steps redone and the tooling around the pipeline unable to report time actually used by tsinfer accurately.
It would be possible to record this information in the provenance field of the tree sequence, steps that are distributed can store their timings and combine them on finalise.
The text was updated successfully, but these errors were encountered:
Tracking wallclock and cpu time used in inference is challenging in the distributed inference pipelines we're running, as they are often interrupted with steps redone and the tooling around the pipeline unable to report time actually used by tsinfer accurately.
It would be possible to record this information in the provenance field of the tree sequence, steps that are distributed can store their timings and combine them on
finalise
.The text was updated successfully, but these errors were encountered: