[perl #131914] [REGRESSION] Rakudo/Moar taking more memory at launch.
Interestingly, I can't reproduce it as well… But the numbers are still higher than they were, so I guess the ticket is valid? Here's the output on all releases: https://gist.github.com/Whateverable/8687cceb1bfcf39e9818cef819d29391 I'd say we can close it once we go back to 50-ish. On 2017-08-17 02:23:26, jn...@jnthn.net wrote: > On Wed, 16 Aug 2017 14:53:05 -0700, alex.jakime...@gmail.com wrote: > > Also, it's not any different on HEAD: > > > > committable6test: 9658dd98c9dd8ec^^,9658dd98c9dd8ec,HEAD > > say > > "/proc/$*PID/statm".IO.lines[0].split(/\s/)[5] * 4096 / 1024 > > AlexDaniel, ¦9658dd98c9dd8ec^^: «58628» ¦9658dd9: > > «138220» > > ¦HEAD(3e70d44): «136436» > > > > On 2017-08-16 14:27:37, alex.jakime...@gmail.com wrote: > > > Note that the tests on 92bd7e4^ and 92bd7e4 are not very related to > > > this > > > particular issue. > > > > > > To put simply: it went from 58628 to 138220 because of changes > > > related > > > to this > > > commit (or maybe one or two commits before it): > > > > > https://github.com/rakudo/rakudo/commit/9658dd98c9dd8ecbefc606a08357e59718e328c2 > > > > > > For Proc → Proc::Async issue see this ticket: > > > https://rt.perl.org/m/ticket/show?id=131915 > > > > > > Bisect logs: > > > https://gist.github.com/6a7a6bfbc157bac3d06e9d2d58306846 > > > https://gist.github.com/5cf477671560bad21251207895708d94 > > > > > > > > > On 2017-08-16 14:21:25, scoli...@gmail.com wrote: > > > > After some test against various release of rakudo it appear that > > > > there > > > > is a huge step in the memory taken by rakudo/moar at launch. > > > > (after > > > > 2017.05) > > > > It's like up to 55Mb to 120Mb+ > > > > > > > > It was tested by reading the memory info in /proc/pid/statm (the > > > > number is in Kbytes) > > > > > > > > committable6test: > > > > 92bd7e4f54a9^,92bd7e4f54a9,9658dd98c9dd8ec^^,9658dd98c9dd8ec say > > > > "/proc/$*PID/statm".IO.lines[0].split(/\s/)[5] * 4096 / 1024 > > > > AlexDaniel, ¦92bd7e4f54a9^: «55752» ¦92bd7e4: > > > > «55896» ¦9658dd98c9dd8ec^^: «58628» ¦9658dd9: «138220» > > I can't reproduce such an sizable increase at HEAD or > MoarVM/NQP/Rakduo: > > $ ./perl6-m -e 'say "/proc/$*PID/statm".IO.lines[0].split(/\s/)[5] * > 4096 / 1024' > 79904
[perl #131914] [REGRESSION] Rakudo/Moar taking more memory at launch.
On Wed, 16 Aug 2017 14:53:05 -0700, alex.jakime...@gmail.com wrote: > Also, it's not any different on HEAD: > > committable6test: 9658dd98c9dd8ec^^,9658dd98c9dd8ec,HEAD > say > "/proc/$*PID/statm".IO.lines[0].split(/\s/)[5] * 4096 / 1024 > AlexDaniel, ¦9658dd98c9dd8ec^^: «58628» ¦9658dd9: > «138220» > ¦HEAD(3e70d44): «136436» > > On 2017-08-16 14:27:37, alex.jakime...@gmail.com wrote: > > Note that the tests on 92bd7e4^ and 92bd7e4 are not very related to > > this > > particular issue. > > > > To put simply: it went from 58628 to 138220 because of changes > > related > > to this > > commit (or maybe one or two commits before it): > > > https://github.com/rakudo/rakudo/commit/9658dd98c9dd8ecbefc606a08357e59718e328c2 > > > > For Proc → Proc::Async issue see this ticket: > > https://rt.perl.org/m/ticket/show?id=131915 > > > > Bisect logs: > > https://gist.github.com/6a7a6bfbc157bac3d06e9d2d58306846 > > https://gist.github.com/5cf477671560bad21251207895708d94 > > > > > > On 2017-08-16 14:21:25, scoli...@gmail.com wrote: > > > After some test against various release of rakudo it appear that > > > there > > > is a huge step in the memory taken by rakudo/moar at launch. (after > > > 2017.05) > > > It's like up to 55Mb to 120Mb+ > > > > > > It was tested by reading the memory info in /proc/pid/statm (the > > > number is in Kbytes) > > > > > > committable6test: > > > 92bd7e4f54a9^,92bd7e4f54a9,9658dd98c9dd8ec^^,9658dd98c9dd8ec say > > > "/proc/$*PID/statm".IO.lines[0].split(/\s/)[5] * 4096 / 1024 > > > AlexDaniel, ¦92bd7e4f54a9^: «55752» ¦92bd7e4: > > > «55896» ¦9658dd98c9dd8ec^^: «58628» ¦9658dd9: «138220» I can't reproduce such an sizable increase at HEAD or MoarVM/NQP/Rakduo: $ ./perl6-m -e 'say "/proc/$*PID/statm".IO.lines[0].split(/\s/)[5] * 4096 / 1024' 79904
[perl #131914] [REGRESSION] Rakudo/Moar taking more memory at launch.
On Wed, 16 Aug 2017 14:53:05 -0700, alex.jakime...@gmail.com wrote: > Also, it's not any different on HEAD: > > committable6test: 9658dd98c9dd8ec^^,9658dd98c9dd8ec,HEAD > say > "/proc/$*PID/statm".IO.lines[0].split(/\s/)[5] * 4096 / 1024 > AlexDaniel, ¦9658dd98c9dd8ec^^: «58628» ¦9658dd9: > «138220» > ¦HEAD(3e70d44): «136436» > > On 2017-08-16 14:27:37, alex.jakime...@gmail.com wrote: > > Note that the tests on 92bd7e4^ and 92bd7e4 are not very related to > > this > > particular issue. > > > > To put simply: it went from 58628 to 138220 because of changes > > related > > to this > > commit (or maybe one or two commits before it): > > > https://github.com/rakudo/rakudo/commit/9658dd98c9dd8ecbefc606a08357e59718e328c2 > > > > For Proc → Proc::Async issue see this ticket: > > https://rt.perl.org/m/ticket/show?id=131915 > > > > Bisect logs: > > https://gist.github.com/6a7a6bfbc157bac3d06e9d2d58306846 > > https://gist.github.com/5cf477671560bad21251207895708d94 > > > > > > On 2017-08-16 14:21:25, scoli...@gmail.com wrote: > > > After some test against various release of rakudo it appear that > > > there > > > is a huge step in the memory taken by rakudo/moar at launch. (after > > > 2017.05) > > > It's like up to 55Mb to 120Mb+ > > > > > > It was tested by reading the memory info in /proc/pid/statm (the > > > number is in Kbytes) > > > > > > committable6test: > > > 92bd7e4f54a9^,92bd7e4f54a9,9658dd98c9dd8ec^^,9658dd98c9dd8ec say > > > "/proc/$*PID/statm".IO.lines[0].split(/\s/)[5] * 4096 / 1024 > > > AlexDaniel, ¦92bd7e4f54a9^: «55752» ¦92bd7e4: > > > «55896» ¦9658dd98c9dd8ec^^: «58628» ¦9658dd9: «138220» I can't reproduce such an sizable increase at HEAD or MoarVM/NQP/Rakduo: $ ./perl6-m -e 'say "/proc/$*PID/statm".IO.lines[0].split(/\s/)[5] * 4096 / 1024' 79904
[perl #131914] [REGRESSION] Rakudo/Moar taking more memory at launch.
Also, it's not any different on HEAD: committable6test: 9658dd98c9dd8ec^^,9658dd98c9dd8ec,HEAD say "/proc/$*PID/statm".IO.lines[0].split(/\s/)[5] * 4096 / 1024 AlexDaniel, ¦9658dd98c9dd8ec^^: «58628» ¦9658dd9: «138220» ¦HEAD(3e70d44): «136436» On 2017-08-16 14:27:37, alex.jakime...@gmail.com wrote: > Note that the tests on 92bd7e4^ and 92bd7e4 are not very related to > this > particular issue. > > To put simply: it went from 58628 to 138220 because of changes related > to this > commit (or maybe one or two commits before it): > https://github.com/rakudo/rakudo/commit/9658dd98c9dd8ecbefc606a08357e59718e328c2 > > For Proc → Proc::Async issue see this ticket: > https://rt.perl.org/m/ticket/show?id=131915 > > Bisect logs: > https://gist.github.com/6a7a6bfbc157bac3d06e9d2d58306846 > https://gist.github.com/5cf477671560bad21251207895708d94 > > > On 2017-08-16 14:21:25, scoli...@gmail.com wrote: > > After some test against various release of rakudo it appear that > > there > > is a huge step in the memory taken by rakudo/moar at launch. (after > > 2017.05) > > It's like up to 55Mb to 120Mb+ > > > > It was tested by reading the memory info in /proc/pid/statm (the > > number is in Kbytes) > > > > committable6test: > > 92bd7e4f54a9^,92bd7e4f54a9,9658dd98c9dd8ec^^,9658dd98c9dd8ec say > > "/proc/$*PID/statm".IO.lines[0].split(/\s/)[5] * 4096 / 1024 > > AlexDaniel, ¦92bd7e4f54a9^: «55752» ¦92bd7e4: > > «55896» ¦9658dd98c9dd8ec^^: «58628» ¦9658dd9: «138220»
[perl #131914] [Regression] Rakudo/Moar taking more memory at launch.
Note that the tests on 92bd7e4^ and 92bd7e4 are not very related to this particular issue. To put simply: it went from 58628 to 138220 because of changes related to this commit (or maybe one or two commits before it): https://github.com/rakudo/rakudo/commit/9658dd98c9dd8ecbefc606a08357e59718e328c2 For Proc → Proc::Async issue see this ticket: https://rt.perl.org/m/ticket/show?id=131915 Bisect logs: https://gist.github.com/6a7a6bfbc157bac3d06e9d2d58306846 https://gist.github.com/5cf477671560bad21251207895708d94 On 2017-08-16 14:21:25, scoli...@gmail.com wrote: > After some test against various release of rakudo it appear that there > is a huge step in the memory taken by rakudo/moar at launch. (after > 2017.05) > It's like up to 55Mb to 120Mb+ > > It was tested by reading the memory info in /proc/pid/statm (the > number is in Kbytes) > > committable6test: > 92bd7e4f54a9^,92bd7e4f54a9,9658dd98c9dd8ec^^,9658dd98c9dd8ec say > "/proc/$*PID/statm".IO.lines[0].split(/\s/)[5] * 4096 / 1024 > AlexDaniel, ¦92bd7e4f54a9^: «55752» ¦92bd7e4: > «55896» ¦9658dd98c9dd8ec^^: «58628» ¦9658dd9: «138220»
[perl #131914] [Regression] Rakudo/Moar taking more memory at launch.
# New Ticket Created by Sylvain Colinet # Please include the string: [perl #131914] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=131914 > After some test against various release of rakudo it appear that there is a huge step in the memory taken by rakudo/moar at launch. (after 2017.05) It's like up to 55Mb to 120Mb+ It was tested by reading the memory info in /proc/pid/statm (the number is in Kbytes) committable6test: 92bd7e4f54a9^,92bd7e4f54a9,9658dd98c9dd8ec^^,9658dd98c9dd8ec say "/proc/$*PID/statm".IO.lines[0].split(/\s/)[5] * 4096 / 1024 AlexDaniel, ¦92bd7e4f54a9^: «55752» ¦92bd7e4: «55896» ¦9658dd98c9dd8ec^^: «58628» ¦9658dd9: «138220»
