Two problems: One, many call sites really want a two-entry cache (mutable and non-mutable class, for example). Two, it costs too much dirty memory to do this everywhere so you need some way to choose at compile time where to apply it.
I still think PGO would result in wins, but I can understand it being lower priority than in JS.
-
-
Like
@gparker said, the main issue with PGO is the workflow problem of collecting and maintaining good profile info, which AFAIK still hasn’t really been solved well. -
Yup. We used to have problems with MSVC PGO causing *address space* exhaustion on 32-bit build machines :)
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.