Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rakudo/Moar taking more memory at launch. #6448

Open
p6rt opened this issue Aug 16, 2017 · 6 comments
Open

Rakudo/Moar taking more memory at launch. #6448

p6rt opened this issue Aug 16, 2017 · 6 comments
Labels
regression Issue did not exist previously

Comments

@p6rt
Copy link

p6rt commented Aug 16, 2017

Migrated from rt.perl.org#131914 (status was 'open')

Searchable as RT131914$

@p6rt
Copy link
Author

p6rt commented Aug 16, 2017

From @Skarsnik

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)

<AlexDaniel> committable6test​: 92bd7e4f54a9^,92bd7e4f54a9,9658dd98c9dd8ec^^,9658dd98c9dd8ec say "/proc/$*PID/statm".IO.lines[0].split(/\s/)[5] * 4096 / 1024
<committable6test> AlexDaniel, ¦92bd7e4f54a9^​: «55752» ¦92bd7e4​: «55896» ¦9658dd98c9dd8ec^^​: «58628» ¦9658dd9​: «138220»

@p6rt
Copy link
Author

p6rt commented Aug 16, 2017

From @AlexDaniel

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)​: rakudo/rakudo@9658dd9

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, scolinet@​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)

<AlexDaniel> committable6test​:
92bd7e4f54a9^,92bd7e4f54a9,9658dd98c9dd8ec^^,9658dd98c9dd8ec say
"/proc/$*PID/statm".IO.lines[0].split(/\s/)[5] * 4096 / 1024
<committable6test> AlexDaniel, ¦92bd7e4f54a9^​: «55752» ¦92bd7e4​:
«55896» ¦9658dd98c9dd8ec^^​: «58628» ¦9658dd9​: «138220»

@p6rt
Copy link
Author

p6rt commented Aug 16, 2017

The RT System itself - Status changed from 'new' to 'open'

@p6rt
Copy link
Author

p6rt commented Aug 16, 2017

From @AlexDaniel

Also, it's not any different on HEAD​:

<AlexDaniel> committable6test​: 9658dd98c9dd8ec^^,9658dd98c9dd8ec,HEAD say "/proc/$*PID/statm".IO.lines[0].split(/\s/)[5] * 4096 / 1024
<committable6test> AlexDaniel, ¦9658dd98c9dd8ec^^​: «58628» ¦9658dd9​: «138220» ¦HEAD(3e70d44)​: «136436»

On 2017-08-16 14​:27​:37, alex.jakimenko@​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)​:
rakudo/rakudo@9658dd9

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, scolinet@​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)

<AlexDaniel> committable6test​:
92bd7e4f54a9^,92bd7e4f54a9,9658dd98c9dd8ec^^,9658dd98c9dd8ec say
"/proc/$*PID/statm".IO.lines[0].split(/\s/)[5] * 4096 / 1024
<committable6test> AlexDaniel, ¦92bd7e4f54a9^​: «55752» ¦92bd7e4​:
«55896» ¦9658dd98c9dd8ec^^​: «58628» ¦9658dd9​: «138220»

@p6rt
Copy link
Author

p6rt commented Aug 17, 2017

From @jnthn

On Wed, 16 Aug 2017 14​:53​:05 -0700, alex.jakimenko@​gmail.com wrote​:

Also, it's not any different on HEAD​:

<AlexDaniel> committable6test​: 9658dd98c9dd8ec^^,9658dd98c9dd8ec,HEAD
say
"/proc/$*PID/statm".IO.lines[0].split(/\s/)[5] * 4096 / 1024
<committable6test> AlexDaniel, ¦9658dd98c9dd8ec^^​: «58628» ¦9658dd9​:
«138220»
¦HEAD(3e70d44)​: «136436»

On 2017-08-16 14​:27​:37, alex.jakimenko@​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)​:

rakudo/rakudo@9658dd9

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, scolinet@​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)

<AlexDaniel> committable6test​:
92bd7e4f54a9^,92bd7e4f54a9,9658dd98c9dd8ec^^,9658dd98c9dd8ec say
"/proc/$*PID/statm".IO.lines[0].split(/\s/)[5] * 4096 / 1024
<committable6test> 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

@p6rt
Copy link
Author

p6rt commented Mar 11, 2018

From @AlexDaniel

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, jnthn@​jnthn.net wrote​:

On Wed, 16 Aug 2017 14​:53​:05 -0700, alex.jakimenko@​gmail.com wrote​:

Also, it's not any different on HEAD​:

<AlexDaniel> committable6test​: 9658dd98c9dd8ec^^,9658dd98c9dd8ec,HEAD
say
"/proc/$*PID/statm".IO.lines[0].split(/\s/)[5] * 4096 / 1024
<committable6test> AlexDaniel, ¦9658dd98c9dd8ec^^​: «58628» ¦9658dd9​:
«138220»
¦HEAD(3e70d44)​: «136436»

On 2017-08-16 14​:27​:37, alex.jakimenko@​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)​:

rakudo/rakudo@9658dd9

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, scolinet@​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)

<AlexDaniel> committable6test​:
92bd7e4f54a9^,92bd7e4f54a9,9658dd98c9dd8ec^^,9658dd98c9dd8ec say
"/proc/$*PID/statm".IO.lines[0].split(/\s/)[5] * 4096 / 1024
<committable6test> 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

@p6rt p6rt added the regression Issue did not exist previously label Jan 5, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
regression Issue did not exist previously
Projects
None yet
Development

No branches or pull requests

1 participant