| I see similar results when running from a gem using the puppet-runtime from respective puppet-agent builds. Note these use facter 2.x gem: 5.5.x:
PS C:\> Measure-Command {Write-Host $(puppet --version); Write-Host $(ruby --version) } |
5.5.17 |
ruby 2.4.9p362 (2019-10-02 revision 67824) [x64-mingw32] |
|
... |
TotalMilliseconds : 1426.2972
|
6.11.1:
PS C:\> Measure-Command {Write-Host $(puppet --version); Write-Host $(ruby --version) } |
6.11.1 |
ruby 2.5.7p206 (2019-10-01 revision 67816) [x64-mingw32] |
|
... |
TotalMilliseconds : 5376.293
|
Running puppet 6.11.1 on ruby 2.4.9, is also slow, which indicates this a puppet issue more than a 2.4 vs 2.5 ruby issue:
PS C:\> Measure-Command {Write-Host $(puppet --version); Write-Host $(ruby --version) } |
6.11.1 |
ruby 2.4.9p362 (2019-10-02 revision 67824) [x64-mingw32] |
|
... |
TotalMilliseconds : 4067.7442
|
The same facter gem (2.5.6) is a little bit slower on 6.11.1/ruby 2.5.7: 5.5.x
PS C:\> Measure-Command { facter } | Select-Object -Property TotalMilliseconds |
|
TotalMilliseconds |
----------------- |
3822.3564
|
6.11.1
PS C:\> Measure-Command { facter } | Select-Object -Property TotalMilliseconds |
|
TotalMilliseconds |
----------------- |
4228.5548
|
|
