Message 387886 - 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	nascheme
Recipients	methane, nascheme, tim.peters
Date	2021-03-01.23:46:13
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<[email protected]>
In-reply-to

Content
I was curious about the performance impact on a non-AMD64 platform. I run pyperformance using an AWS t4g.micro instance. That's an ARM64 CPU. I did four sets of runs in total and the results seem repeatable, even given the vitalization. I don't know why xml_etree_iterparse is significantly slower. Seems like a spurious anomaly. I was going to try on a m6g.metal instance (bare metal, no virtualization) by my AWS account doesn't allow that many vCPUs it seems.

I was curious about the performance impact on a non-AMD64 platform.  I run pyperformance using an AWS t4g.micro instance.  That's an ARM64 CPU.  I did four sets of runs in total and the results seem repeatable, even given the vitalization.  I don't know why xml_etree_iterparse is significantly slower.  Seems like a spurious anomaly.

I was going to try on a m6g.metal instance (bare metal, no virtualization) by my AWS account doesn't allow that many vCPUs it seems.

History
Date	User	Action	Args
2021-03-01 23:46:14	nascheme	set	recipients: + nascheme, tim.peters, methane
2021-03-01 23:46:14	nascheme	set	messageid: <[email protected]>
2021-03-01 23:46:14	nascheme	link	issue37448 messages
2021-03-01 23:46:13	nascheme	create