Message 227872 - Python tracker

➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author	lemburg
Recipients	BreamoreBoy, lemburg, pitrou
Date	2014-09-30.09:23:13
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1412068994.52.0.379733212538.issue4093@psf.upfronthosting.co.za>
In-reply-to

Content
I think it's better to keep pybench speed performance oriented and rather use a new tool for memory performance tests. I've recently done a lightning talk at PyCon UK on the subject and found the current tools we have for memory testing a bit underdeveloped: http://www.egenix.com/library/presentations/PyCon-UK-2014-When-performance-matters/ As s result, I wrote some support helpers for this, which can be found in perftools.py on: https://github.com/egenix/when-performance-matters Perhaps this will some day turn into a pymembench :-) For now, I'm closing the ticket.

I think it's better to keep pybench speed performance oriented and rather use a new tool for memory performance tests.

I've recently done a lightning talk at PyCon UK on the subject and found the current tools we have for memory testing a bit underdeveloped:

http://www.egenix.com/library/presentations/PyCon-UK-2014-When-performance-matters/

As s result, I wrote some support helpers for this, which can be found in perftools.py on:

https://github.com/egenix/when-performance-matters

Perhaps this will some day turn into a pymembench :-)

For now, I'm closing the ticket.

History
Date	User	Action	Args
2014-09-30 09:23:14	lemburg	set	recipients: + lemburg, pitrou, BreamoreBoy
2014-09-30 09:23:14	lemburg	set	messageid: <1412068994.52.0.379733212538.issue4093@psf.upfronthosting.co.za>
2014-09-30 09:23:14	lemburg	link	issue4093 messages
2014-09-30 09:23:13	lemburg	create