Closed nkrusch closed 3 years ago
Neat, thanks.
Unless we have any reason to think that the examples we have are absolutely not representative, that seems to be a success.
For easier comparison:
/ | function calls | primitive calls | time |
---|---|---|---|
before | 13 224 063 | 10 707 799 | 5.163 |
after | 2 561 855 | 2 483 457 | 1.328 |
"winner" | after | after | after |
/ | function calls | primitive calls | time |
---|---|---|---|
before | 15 474 866 | 13 029 729 | 6.015 |
after | 2 463 339 | 2 391 520 | 1.308 |
"winner" | after | after | after |
This is a good improvement, first time I profiled these in Jan these same times were ~23s. I have also checked code quality and everything looks great there, well documented and good Python style.
Time for a PR?
Youp. I'll let you take care of it. And close this issue?
Really nice ! Thanks @nkrusch !
for_body.c
cannot be parsed and throwsSome comparisons ordered by internal time:
infinite_8.c
before: 13224063 function calls (10707799 primitive calls) in 5.163 seconds
after: 2561855 function calls (2483457 primitive calls) in 1.328 seconds
notinfinite_8.c
before: 15474866 function calls (13029729 primitive calls) in 6.015 seconds
after: 2463339 function calls (2391520 primitive calls) in 1.308 seconds
To profile individual C file, the command is:
-m pymwp
to profile using old Analysis.py (though it pauses for user input so might not work?)c_files/infinite_2.c
with whatever input you want to profile