如何在PowerShell类构造函数中实现异步或并行处理？

要解决构造函数中同步执行耗时操作导致的实例创建缓慢问题，核心思路是将耗时的数据获取逻辑从构造函数中剥离，改用PowerShell的并发机制并行处理数据采集，最后再将结果注入类实例。以下是几种实用的实现方案：

第一步：重构类的设计 #

首先调整Server类的构造函数，使其只负责接收预获取的数据，而非在内部执行同步查询：

Class Server {
    [string]$ServerName
    [psobject]$ComputerSystem
    [psobject]$OperatingSystem
    [psobject]$Bios
    [psobject]$NetworkAdapter

    Server([string]$ServerName, [psobject]$ComputerSystem, [psobject]$OperatingSystem, [psobject]$Bios, [psobject]$NetworkAdapter) {
        $this.ServerName = $ServerName
        $this.ComputerSystem = $ComputerSystem
        $this.OperatingSystem = $OperatingSystem
        $this.Bios = $Bios
        $this.NetworkAdapter = $NetworkAdapter
    }
}

方案1：使用ForEach-Object -Parallel（PowerShell 7+推荐） #

这是语法最简洁的并发方式，适合PowerShell 7及以上版本，性能优于后台作业：

# 待处理的服务器列表
$serverNames = @("Server01", "Server02", "Server03")

# 并发获取数据并创建实例
$serverInstances = $serverNames | ForEach-Object -Parallel {
    $serverName = $_
    try {
        # 并行执行所有CIM查询
        $computerSystem = Get-CimInstance Win32_ComputerSystem -ComputerName $serverName -ErrorAction Stop
        $os = Get-CimInstance Win32_OperatingSystem -ComputerName $serverName -ErrorAction Stop
        $bios = Get-CimInstance Win32_BIOS -ComputerName $serverName -ErrorAction Stop
        $network = Get-CimInstance Win32_NetworkAdapterConfiguration -ComputerName $serverName -ErrorAction Stop

        # 创建并返回Server实例
        [Server]::new($serverName, $computerSystem, $os, $bios, $network)
    } catch {
        Write-Warning "服务器 $serverName 处理失败: $_"
        return $null
    }
} -ThrottleLimit 5  # 控制并发数，根据资源情况调整

方案2：使用RunspacePool（兼容PowerShell 5.x，高效轻量） #

如果仍在使用PowerShell 5.x，RunspacePool是比后台作业更高效的选择（避免进程级开销）：

$serverNames = @("Server01", "Server02", "Server03")
$throttleLimit = 5

# 创建Runspace池，控制并发数
$runspacePool = [runspacefactory]::CreateRunspacePool(1, $throttleLimit)
$runspacePool.Open()

$jobs = @()

foreach ($serverName in $serverNames) {
    $scriptBlock = {
        param($serverName)
        try {
            $computerSystem = Get-CimInstance Win32_ComputerSystem -ComputerName $serverName -ErrorAction Stop
            $os = Get-CimInstance Win32_OperatingSystem -ComputerName $serverName -ErrorAction Stop
            $bios = Get-CimInstance Win32_BIOS -ComputerName $serverName -ErrorAction Stop
            $network = Get-CimInstance Win32_NetworkAdapterConfiguration -ComputerName $serverName -ErrorAction Stop
            [Server]::new($serverName, $computerSystem, $os, $bios, $network)
        } catch {
            Write-Warning "服务器 $serverName 处理失败: $_"
            return $null
        }
    }

    # 创建PowerShell实例并绑定到Runspace池
    $ps = [powershell]::Create().AddScript($scriptBlock).AddParameter("serverName", $serverName)
    $ps.RunspacePool = $runspacePool

    # 异步启动任务
    $jobs += [pscustomobject]@{
        PowerShell = $ps
        AsyncResult = $ps.BeginInvoke()
    }
}

# 收集所有任务结果
$serverInstances = @()
foreach ($job in $jobs) {
    $serverInstances += $job.PowerShell.EndInvoke($job.AsyncResult)
    $job.PowerShell.Dispose()
}

# 清理资源
$runspacePool.Close()
$runspacePool.Dispose()

方案3：使用后台作业（兼容性最好，开销较大） #

后台作业兼容所有PowerShell版本，但每个作业会启动独立进程，适合少量服务器场景：

$serverNames = @("Server01", "Server02", "Server03")

# 启动后台作业
$jobs = $serverNames | ForEach-Object {
    Start-Job -ScriptBlock {
        param($serverName)
        try {
            $computerSystem = Get-CimInstance Win32_ComputerSystem -ComputerName $serverName -ErrorAction Stop
            $os = Get-CimInstance Win32_OperatingSystem -ComputerName $serverName -ErrorAction Stop
            $bios = Get-CimInstance Win32_BIOS -ComputerName $serverName -ErrorAction Stop
            $network = Get-CimInstance Win32_NetworkAdapterConfiguration -ComputerName $serverName -ErrorAction Stop
            [Server]::new($serverName, $computerSystem, $os, $bios, $network)
        } catch {
            Write-Warning "服务器 $serverName 处理失败: $_"
            return $null
        }
    } -ArgumentList $_
}

# 等待作业完成并获取结果
$serverInstances = $jobs | Receive-Job -Wait -AutoRemoveJob

关键注意事项 #

• 控制并发数：根据本地系统资源和目标服务器的承受能力调整并发上限，避免因过载导致超时或连接失败。
• 错误处理：必须添加try/catch捕获CIM连接异常，防止单个任务失败影响整体流程。
• 资源清理：使用Runspace或后台作业后，务必及时释放资源，避免内存泄漏。

内容的提问来源于stack exchange，提问作者end-user