-
Notifications
You must be signed in to change notification settings - Fork 24
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
Refactor timing tests #42
Refactor timing tests #42
Conversation
Task manager shows Python taking up 5GB of memory with these tests running, we probably have a leak. |
Undoubtably. I left a lot of the cleanup as a TODO. :-( How does this relate to #41? Should I merge that first or is this the same? |
This builds on top of #41. I'd merge that one because it's ready. This one I'll mark as draft, I'm not as sure about it. |
Okay, I pushed #41, so this one then reduces to just the last commit,
right? Can you rebase and push?
|
Maybe make the column align?
I've also wondered if this should live in its own file under Tools/pyco,
rather than in the tests -- we don't really want speed tests to be run as
part of a typical test run.
|
7919b27
to
788e36e
Compare
Yes, I'll make it a separate script and we can export a csv and then look at the number how we want. |
That would be much appreciated. That said, I discussed the status of my branch with Mark this morning, and we agreed to pause development and try some other experiments before we go further down this road. See this comment for details. |
788e36e
to
edf994d
Compare
edf994d
to
8fc836b
Compare
This leaves the unit tests intact and add a Tools script that creates a csv like this: num_funcs,func_length,num_vars,is_locals,is_unique_names,is_vary_constants,is_call,load+exec,steady-state |
I see where you're coming from with the other directions. My takeaway so far is that we haven't squeezed what we can from this branch, but it would take quite a lot to, essentially, replicate what marshal does in a lazy way. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why not just delete the speed tests from test_pyc_new.py?
And maybe add a flag to perf_micro.py to keep the old formatting? (I'm not a data scientist and I don't want to become one -- I have no idea what people do with CSV these days. :-)
We certainly could squeeze more (and research more), but I don't know if it would be sufficient, and I'd prefer not to have to much more work when we're not sure that this is the direction we want to take. So I'd like to explore a few other things before deciding to pick this back up. |
Now it's all in the Tools/ script, writes like before to the screen and optionally also a csv to a file. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Success!
The idea here is to make the tests more configurable, so we can see how they scale.
These are results from a Mac. On the windows box the current test chokes to computer, I think there's a bug somewhere because these tests are not huge.