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 | gregory.p.smith |
|---|---|
| Recipients | gregory.p.smith, jyasskin, nnorwitz, skip.montanaro |
| Date | 2008年03月18日.07:10:51 |
| SpamBayes Score | 0.26604006 |
| Marked as misclassified | No |
| Message-id | <1205824252.06.0.994804723483.issue2262@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
We really could use an automated pybench runner on a dedicated machine driven by a buildbot feeding its results into a database so that we had a record of exactly when/what caused performance changes over time. This sounds remarkably like some of the work I was doing at my last job... ;) I'll run some benchmarks using this patch of my own and on the grander scale ponder what I need to make a dedicated automated Python benchmark server happen. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2008年03月18日 07:10:52 | gregory.p.smith | set | spambayes_score: 0.26604 -> 0.26604006 recipients: + gregory.p.smith, skip.montanaro, nnorwitz, jyasskin |
| 2008年03月18日 07:10:52 | gregory.p.smith | set | spambayes_score: 0.26604 -> 0.26604 messageid: <1205824252.06.0.994804723483.issue2262@psf.upfronthosting.co.za> |
| 2008年03月18日 07:10:51 | gregory.p.smith | link | issue2262 messages |
| 2008年03月18日 07:10:51 | gregory.p.smith | create | |