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
A 1.0 of ParallelZone requires the Python API to be finalized, decently performant, and unit tested. To that end I started PR: #74. The aforementioned PR currently showcases several of the more general issues found on the Python API project board.
I specifically want to call out (sub bullets refer back to the #74):
The serial Python unit tests barely do anything and they take over 5x longer than the C++ tests
I haven't profiled, but I'm guessing this is import overhead, this issue should be updated if it's not
This is based on the times from Python unittest times being similar to the C++ times, but the final wall time is one to two orders of magnitude slower.
The MPI overhead is visible, but admittedly not too appreciable at this point (about half a second; C++ unit tests saw half that). It's possible that fleshing out more unit tests may add to to the overhead, or that we can ignore the overhead for ParallelZone. More profiling should be done.
A 1.0 of ParallelZone requires the Python API to be finalized, decently performant, and unit tested. To that end I started PR: #74. The aforementioned PR currently showcases several of the more general issues found on the Python API project board.
I specifically want to call out (sub bullets refer back to the #74):
unittest
times being similar to the C++ times, but the final wall time is one to two orders of magnitude slower.__init__.py
file (more general issue)The text was updated successfully, but these errors were encountered: