Open alexdesiqueira opened 4 years ago
I presume this is because we pass in large NumPy arrays. Why would they say this is a joblib issue? It takes time to checksum a large array. Maybe check with the joblib folks?
There are issues opened in joblib
in the same fashion, the most recent one from eight days ago. @AdamGleave suggests a workaround in this one:
As a workaround I am currently using
np.set_printoptions
to reduce the verbosity of repr(x) on a NumPy array x. We could potentially use the same trick in _persist_input (restoring the original options with a {get,set}_printoptions pair), but this does not feel very satisfactory.
Maybe it suits us...? I'll have to check the code.
I'm receiving
joblib
warnings on "persisting input arguments"Should we worry about that? Thank you!