-
-
Notifications
You must be signed in to change notification settings - Fork 18.5k
PERF: asv for import time #26663
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Yea I think this would be a good idea. Maybe create a subprocess in setup and load pandas in the subprocess call |
Here is something similar numpy did: https://github.com/numpy/numpy/pull/8159/files - do we just want to benchmark |
Makes sense to me. I think we'd take a PR for something like that if you'd like to post one |
Ideally, the setup would ensure that matplotlib and numexpr (really, all our optional deps) aren’t in the Python env running the benchmark.
… On Jun 8, 2019, at 15:50, William Ayd ***@***.***> wrote:
Makes sense to me. I think we'd take a PR for something like that if you'd like to post one
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
No opinion on numexpr, but for matplotlib I'd rather it be installed. I'm pretty sure some effort has been put in to making matplotlib imports lazy. This would help ensure that we don't accidentally undo that (this was motivated by exactly this happening in statsmodels) |
Matplotlib has to be imported by default right now because we register formatters. That’s deprecated, and then we can ensure it’s lazily imported.
We have a separate CI check ensuring that certain packages aren’t imported with pandas (search for import time)
… On Jun 9, 2019, at 10:33, jbrockmendel ***@***.***> wrote:
No opinion on numexpr, but for matplotlib I'd rather it be installed. I'm pretty sure some effort has been put in to making matplotlib imports lazy. This would help ensure that we don't accidentally undo that (this was motivated by exactly this happening in statsmodels)
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Line 192 in c7748ca
|
Thanks for pointing that out. Is there a particular reason that was used instead of the approach here statsmodels/statsmodels#5831 ? |
You mean a separate check, not run as part of the pytest test suite? Probably no reason; seems easier to me that it be separate since it isn’t really a traditional unit test.
… On Jun 9, 2019, at 11:43, jbrockmendel ***@***.***> wrote:
Thanks for pointing that out. Is there a particular reason that was used instead of the approach here statsmodels/statsmodels#5831 ?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Not entirely sure how to do it with asv, but at the command line its just
python3 -X importtime -c "import pandas"
python3 -X importtime -c "import pandas"
import pandas, psutil; psutil.Process().memory_info()
The text was updated successfully, but these errors were encountered: