I want to be clear about something. In theory, we could turn on runtime trace guided optimization for _every_ binary. Python isn't particularly special on this. It would also, in my opinion, be a horrible mistake -- the benefits are fairly small compared to the astonishing build times. There are people for whom this is important, but they're not normal users.
Perry On Sun, 15 Jul 2018 16:46:59 -0700 Eitan Adler <[email protected]> wrote: > On Sun, 15 Jul 2018 at 13:30, Perry E. Metzger > <[email protected]> wrote: > > It can take tens of minutes instead of a minute or two to build > > when you turn it on. That's quite different from the fairly slight > > change that normal optimization brings. > > Does it change the amount of time to install a binary package? For > most users the cost will be paid by the builders, not the users. > > > Indeed, for some people, the > > extra time for the build may significantly exceed the sum of the > > gains they ever experience running Python over the lifetime of > > the binaries. > > And those people can turn it off. > > > It is thus now available for users, but not the default. > > And this is a mistake. > > -- Perry E. Metzger [email protected]
