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
The allow_read_errors_with_report option in uproot.dask is convenient not only to understand issues but also to study performance. While the duration seems to always get filled, I see call_time with None values for successful tasks. Unless this would be a performance issue, I believe that always (or optionally, controlled in some manner) filling this value would be useful. I would be particularly interested in using this to calculate instantaneous data rates (as this opens up the possibility to calculate data read by each task, alongside all required time stamps).
The text was updated successfully, but these errors were encountered:
I also am wondering if the kwarg name for this is possibly confusing: the report can be useful even when read errors are not a concern but the kwarg makes it sound very focused on the "read error" part and not so much on the "report" part. It might not be the most obvious setting to find for people interested in more information.
The
allow_read_errors_with_report
option inuproot.dask
is convenient not only to understand issues but also to study performance. While theduration
seems to always get filled, I seecall_time
withNone
values for successful tasks. Unless this would be a performance issue, I believe that always (or optionally, controlled in some manner) filling this value would be useful. I would be particularly interested in using this to calculate instantaneous data rates (as this opens up the possibility to calculate data read by each task, alongside all required time stamps).The text was updated successfully, but these errors were encountered: