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 eric.snow
Recipients brett.cannon, corona10, eric.snow, lemburg
Date 2021-10-20.15:32:49
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CALFfu7Cp7RYnHkz0opD_XCwZTb6Qv2hn0_1pCsXPBLbNSKBc3w@mail.gmail.com>
In-reply-to <6986df3a-f5cf-786c-6483-20440d7311b2@egenix.com>
Content
On Wed, Oct 20, 2021 at 8:38 AM Marc-Andre Lemburg
<report@bugs.python.org> wrote:
> Yes, 3.10 is next, once I have 3.9 ironed out. And then I'll give 3.11 a try.

Thanks!

> Sorry, I wasn't clear. PGO is not a problem for test_embed. I just
> wonder why the test_embed tests are run for creating the PGO profile
> files. test_embed is far from being a regular work load for Python
> applications.
>
> Well, I guess using the test suite for PGO is questionable anyway.
> It's just that we don't have anything else handy to create those
> profiles at Python build time :-)

Ah, that makes sense.  I expect we don't do anything more complex than
run the whole suite.  There have been discussions in the past about
alternate workloads, but clearly nothing came of that.  I suppose a
comprehensive suite of high-level, (relatively) long-running
benchmarks that cover the community's primary Python workloads would
be ideal, but we don't have anything like that (yet).  I suppose this
is something we could discuss elsewhere. :)
History
Date User Action Args
2021-10-20 15:32:49eric.snowsetrecipients: + eric.snow, lemburg, brett.cannon, corona10
2021-10-20 15:32:49eric.snowlinkissue45395 messages
2021-10-20 15:32:49eric.snowcreate