[Python-Dev] Benchmarking Python 3.3 against Python 2.7 (wide build) (original) (raw)
Brett Cannon brett at python.org
Mon Oct 1 03:41:30 CEST 2012
- Previous message: [Python-Dev] Benchmarking Python 3.3 against Python 2.7 (wide build)
- Next message: [Python-Dev] Benchmarking Python 3.3 against Python 2.7 (wide build)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Sun, Sep 30, 2012 at 8:14 PM, Gregory P. Smith <greg at krypto.org> wrote:
Interesting results!
Another data point for the benchmarks that would be interesting is memory consumption of the python process during the runs. In 3.3 a reasonable place to gather this would be to add a callback to the new gc.callbacks and save a snapshot of the process's memory usage before every collection to gather peak, average and median usage over the life of the process. 2.7 doesn't have this feature but there is a backport of this to 2.7 in the bugtracker. I guess I should join speed@ :) There is already support in perf.py to track memory:
-m, --track_memory Track memory usage. This only works on Linux. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20120930/9f55a876/attachment.html>
- Previous message: [Python-Dev] Benchmarking Python 3.3 against Python 2.7 (wide build)
- Next message: [Python-Dev] Benchmarking Python 3.3 against Python 2.7 (wide build)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]