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
Proc using more memory since being a Proc::Async #6449
Comments
From @SkarsnikSimilar to https://rt.perl.org/m/ticket/show?id=131914 it was noticed that there is a huge increase of memory usage after running a simple echo command. <AlexDaniel> commit: 92bd7e4f54a9^,92bd7e4f54a9,9658dd98c9dd8ec^^,9658dd98c9dd8ec sub mem { "/proc/$*PID/statm".IO.lines[0].split(/\s/)[5] * 4096 / 1024 }; say mem(); run 'echo'; say mem() |
From @AlexDanielTL;DR it went from 59820 to 215976 after this commit: rakudo/rakudo@92bd7e4 Bisect log: On 2017-08-16 14:24:48, scolinet@gmail.com wrote:
|
The RT System itself - Status changed from 'new' to 'open' |
From @AlexDanielhttps://irclog.perlgeek.de/perl6-dev/2017-08-17#i_15032963 On 2017-08-16 14:30:42, alex.jakimenko@gmail.com wrote:
|
From @jnthnOn Wed, 16 Aug 2017 14:24:48 -0700, scolinet@gmail.com wrote:
We won't get it back to where it was, because threads cost something. And we'd not really want to go back to where we were, because Proc had all kinds of ways of not working. It's easy to be cheaper if you can be brokener too. The cost is now very significantly lower, however, thanks to: * The new scheduler, which doesn't wastefully start a load of threads for a single Proc::Async usage. This was the major win. So rather than it causing a 3.8 times growth in program memory size, I now measure it as less than 1.5 (and, better, it won't increase with follow-up calls to run the way it used to either). |
@jnthn - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#131915 (status was 'resolved')
Searchable as RT131915$
The text was updated successfully, but these errors were encountered: