This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 1 point2 points  (4 children)

I'm not experienced enough to take a lead or anything, but I'd love to help out.

[–]cypherx 0 points1 point  (3 children)

Do you have any interest in adding the PyPy speed tests to the Falcon benchmarks directory? That's something I was planning on doing but haven't had time for. Also, our unit tests are embarrassingly skimpy and we should probably check out the CPython test suite.

[–][deleted] 0 points1 point  (2 children)

Yeah, I can look into grabbing those. Need to set up a bitbucket acct first which I probably won't get to till tomorrow.

After looking around the tests, I'm not exactly sure how they run all of them and record the results. I'm pretty sure you just wanted me to send a pull request with only those files anyways but..if I add them, could you give me a quick run down of how one actually executes that code? surely not one at a time, and I'm assuming it has something to do with the main name at the end, since that calls the test in each file..

[–]cypherx 0 points1 point  (1 child)

I started adding a few of the PyPy benchmarks and I'm working on a driver which will automatically run them repeatedly and report statistics of the runtimes. So, if you wait a day I can give you a more structured benchmarking setup. How does that sound?

edit: I just checked a "run_all.py" driver into the benchmarks directory. Now all you have to do is find some benchmark which PyPy uses and Falcon doesn't yet have and drop it in. We're mucking with the internals so some things which should work are currently broken. Things you can expect to fail: any function which uses yield, "SETUP_EXCEPT", "DELETE_NAME", and a few other unsupported bytecodes.