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
extracting data from h5py and h5pyd using a list is slow.
A possible solution is:
The most performant solution would be to use concurrent futures to extract each item associated with the list in parallel and then recombine the requests. This would greatly simplify the logic noted above. The only issue is that it wouldn't be compatible with the already parallel nature of reV Generation as you can't run parallel workers on parellel workers.
Why this feature is necessary:
Even with the slicing tricks implemented here:
rex/rex/resource.py
Lines 133 to 445 in ae280db
extracting data from h5py and h5pyd using a list is slow.
A possible solution is:
The most performant solution would be to use concurrent futures to extract each item associated with the list in parallel and then recombine the requests. This would greatly simplify the logic noted above. The only issue is that it wouldn't be compatible with the already parallel nature of reV Generation as you can't run parallel workers on parellel workers.
Additional Context
Relevant for: NREL/reV#335
Charge code
reV
Urgency / Timeframe
TBD
The text was updated successfully, but these errors were encountered: