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
We are currently blind in our process/profiling logger to any bashlib-based processors (which step ran and how much time was spent).
Implementing this with bash is probably not so easy – you have to keep track of and aggregate CPU-time from all subprocesses forked by the shell through the script.
The text was updated successfully, but these errors were encountered:
So this would require a rewrite of all bashlib processors – but we need to do that anyway. (And the page loop is usually based on our input_files array now, but still clumsy and requires lots of boilerplate.)
We are currently blind in our process/profiling logger to any bashlib-based processors (which step ran and how much time was spent).
Implementing this with bash is probably not so easy – you have to keep track of and aggregate CPU-time from all subprocesses forked by the shell through the script.
The text was updated successfully, but these errors were encountered: