[Python-Dev] performance testing recommendations in devguide
Ezio Melotti
ezio.melotti at gmail.com
Thu May 30 22:35:07 CEST 2013
More information about the Python-Dev mailing list
Thu May 30 22:35:07 CEST 2013
- Previous message: [Python-Dev] performance testing recommendations in devguide
- Next message: [Python-Dev] Segmentation fault on 3.4 with --pydebug
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Hi, On Wed, May 29, 2013 at 9:00 PM, Eric Snow <ericsnowcurrently at gmail.com> wrote: > ... > > What would be important to say in the devguide regarding Python > performance and testing it? In the devguide I would only add information that are specific to benchmarking the interpreter. A separate "Benchmarking HOWTO" that covers generic topics could/should be added to docs.python.org. Best Regards, Ezio Melotti > What would you add/subtract from the > above? How important is testing memory performance? How do we avoid > performance regressions? Thanks! > > -eric
- Previous message: [Python-Dev] performance testing recommendations in devguide
- Next message: [Python-Dev] Segmentation fault on 3.4 with --pydebug
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list