10 Jul
2019
10 Jul
'19
1:54 p.m.
On Wed, Jul 10, 2019 at 5:18 PM Neil Schemenauer
On 2019-07-09, Inada Naoki wrote:
PyObject_Malloc inlines pymalloc_alloc, and PyObject_Free inlines pymalloc_free. But compiler doesn't know which is the hot part in pymalloc_alloc and pymalloc_free.
Hello Inada,
I don't see this on my PC. I'm using GCC 8.3.0. I have configured the build with --enable-optimizations.
I didn't use PGO and that's why GCC didn't know which part is hot.
Maybe, pymalloc performance is similar to mimalloc when PGO is used,
but I had not confirmed it.
While Linux distributions are using PGO, some people use non-PGO Python
(Homebrew, pyenv, etc...). So better performance without PGO is worth.
Regards,
--
Inada Naoki