[issue26233] select.epoll.poll() should avoid calling malloc() each time

STINNER Victor added the comment: Serhiy Storchaka: "I'm not sure that it is worth to apply this optimization. The patch adds half a hundred lines of complex code for only 80 ns benefit. On my computer just incrementing an integer takes 100 ns." Yury Selivanov: "(...) Right, but there are so m

[issue26233] select.epoll.poll() should avoid calling malloc() each time

Yury Selivanov added the comment: > Aside of the performance, my colleague also told me that heavy pressure on > the memory allocator can slowly create framgmentation of the heap memory, > which is true. Right, but there are so many other things which contribute to the memory fragmentation..

[issue26233] select.epoll.poll() should avoid calling malloc() each time

Serhiy Storchaka added the comment: I'm not sure that it is worth to apply this optimization. The patch adds half a hundred lines of complex code for only 80 ns benefit. On my computer just incrementing an integer takes 100 ns. -- ___ Python tracker

[issue26233] select.epoll.poll() should avoid calling malloc() each time

STINNER Victor added the comment: @Yury, Serhiy: Do you think that it's worth to avoid malloc in epoll? Aside of the performance, my colleague also told me that heavy pressure on the memory allocator can slowly create framgmentation of the heap memory, which is true. -- __

[issue26233] select.epoll.poll() should avoid calling malloc() each time

Changes by STINNER Victor : -- title: select.epoll.poll() should away calling malloc() each time -> select.epoll.poll() should avoid calling malloc() each time ___ Python tracker __