🦋 Welcome to the IRC channel of the core developers of the Raku Programming Language (raku.org #rakulang). This channel is logged for the purpose of history keeping about its development | evalbot usage: 'm: say 3;' or /msg camelia m: ... | log inspection situation still under development | For MoarVM see #moarvm
Set by lizmat on 22 May 2021.
Geth rakudo/vrurg-unlimited-threads: 4e56f241d8 | (Elizabeth Mattijsen)++ (committed by Vadim Belman) | src/core.c/ThreadPoolScheduler.pm6
Add :max_threads(*|Inf) as option to ThreadPoolScheduler

For those of us brave enough to not want to be stopped by a maximum number of OS threads. Specifying * or Inf will internally store the value 9223372036854775807 (aka the current maximum value for an uint attribute). The accessor will return Inf if this value is found.		 01:31
rakudo/vrurg-unlimited-threads: 49172cb140 | (Vadim Belman)++ | src/core.c/ThreadPoolScheduler.pm6
Support for setting unlimited max_threads from environment

Extending PR #4941.
Aside of just setting `$!max_threads` to a specific number via
  `RAKUDO_MAX_THREADS` environment variable the following special cases
are now supported too: ... (23 more lines)
rakudo: vrurg++ created pull request #4941:
Allow setting ThreadPoolScheduler's max_threads to semi-infinite value		 01:35
rakudo/vrurg-unlimited-threads: b0ebb5e610 | (Vadim Belman)++ | src/core.c/ThreadPoolScheduler.pm6
Support for setting unlimited max_threads from environment

Extending PR #4931.
Aside of just setting `$!max_threads` to a specific number via
  `RAKUDO_MAX_THREADS` environment variable the following special cases
are now supported too: ... (23 more lines)
releasable6 Next release in ≈2 days and ≈11 hours. There are no known blockers. Please log your changes in the ChangeLog: github.com/rakudo/rakudo/wiki/ChangeLog-Draft 07:00
dogbert17 lizmat: are you still happy with your M1 Mac Mini or have any problems surfaced? 10:37
I was a bit interested in the performance of test-t now that you have a faster CPU but no jit 10:58
lizmat dogbert17: old MBP / new MacMini: .867 / .837 11:25
the version with 200K lines: 11.476 / 12.791 11:28
so I'd say for longer running processes, the JIT still makes a difference
with JIT disabled on the old MBP: 1.26 11:29
m: say .867 / 1.26 11:30
camelia 0.688095
lizmat m: say 1.26 / .867
camelia 1.453287
lizmat so the JIT makes the 10K ine about 45% faster
for the 200K version: 11:31
m: say 19.92 / 11.476 11:32
camelia 1.735796
lizmat 70% faster or the 200K version
dogbert17 interesting stats 12:36
vrurg greppable6: initial_threads 13:37
greppable6 vrurg, 5 lines, 4 modules: gist.github.com/22d4da0d466bc021f7...9308f51883
Geth rakudo/vrurg-unlimited-threads: febff8fb7c | (Vadim Belman)++ | src/core.c/ThreadPoolScheduler.pm6
Fix JVM build

This would be more correct approach for MoarVM backend too.
  - Removed `$.initial_threads` attribute because it is only used at the
   construction stage and is not needed otherwise.		 14:29
Geth rakudo/master: 4 commits pushed by (Elizabeth Mattijsen)++, (Vadim Belman)++ 21:00

Powered by Cro and the Raku® Programming Language.

Please report any issues / comments / feature requests as an issue on App::Raku::Log.

Thank you!