a11810bf33
Major changes are as follows: - Avoid `SecuritySupport.IsProductBinary` and unnecessary AMSI/suspicious code scan at startup time - Update `CompiledScriptBlockData.IsProductCode` to avoid unnecessary calls to `IsProductBinary`, which attempts to retrieve catalog signature of the target file. - Update `PerformSecurityChecks` to skip AMSI and suspicious code scan for the `.psd1` file that contains a safe `HashtableAst` only. - Use customized `ReadOnlyBag` instead of `ImmutableHashSet` so that we can avoid loading the `System.Collections.Immutable.dll` completely. - Replace `SHA1` with `CRC32` when generating module analysis cache file name - This remove the loading of `System.Security.Cryptography.Algorithms.dll` at startup - Move `ConvertFrom-SddlString` to C# to remove the `Utility.psm1` file. - Crossgen `Microsoft.ApplicationInsights.dll` and enable tiered compilation - Even pwsh with crossgen assemblies spends a lot time in jitting at the startup, about `191.6ms` comparing with `24.7ms` for Windows PowerShell. - Jitting `Microsoft.ApplicationInsights.dll` takes about `51.6ms`. - By crossgen `Microsoft.ApplicationInsights.dll` and enable tiered compilation, the jitting time drops to about `98.9ms`. |
||
|---|---|---|
| .. | ||
| CimCmdlets | ||
| Microsoft.PowerShell.Core | ||
| Microsoft.PowerShell.Diagnostics | ||
| Microsoft.Powershell.Host | ||
| Microsoft.PowerShell.LocalAccounts | ||
| Microsoft.PowerShell.Management | ||
| Microsoft.PowerShell.Security | ||
| Microsoft.PowerShell.Utility | ||
| Microsoft.WSMan.Management | ||
| PackageManagement | ||
| PowerShellGet | ||
| PSDesiredStateConfiguration | ||
| PSReadLine | ||
| ThreadJob | ||