On Sun, Sep 30, 2012 at 8:14 PM, Gregory P. Smith <g...@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.
_______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
