-
Notifications
You must be signed in to change notification settings - Fork 8.4k
Start-Job is now 6-10x slower, and does not preserve $env:PSModulePath #7402
Copy link
Copy link
Closed
Labels
Issue-Discussionthe issue may not have a clear classification yet. The issue may generate an RFC or may be reclassifthe issue may not have a clear classification yet. The issue may generate an RFC or may be reclassifResolution-No ActivityIssue has had no activity for 6 months or moreIssue has had no activity for 6 months or moreWG-Engine-Performancecore PowerShell engine, interpreter, and runtime performancecore PowerShell engine, interpreter, and runtime performance
Metadata
Metadata
Assignees
Labels
Issue-Discussionthe issue may not have a clear classification yet. The issue may generate an RFC or may be reclassifthe issue may not have a clear classification yet. The issue may generate an RFC or may be reclassifResolution-No ActivityIssue has had no activity for 6 months or moreIssue has had no activity for 6 months or moreWG-Engine-Performancecore PowerShell engine, interpreter, and runtime performancecore PowerShell engine, interpreter, and runtime performance
Type
Fields
Give feedbackNo fields configured for issues without a type.
Steps to reproduce
Expected behavior
I should be able to kick off ten jobs in just a few seconds (maybe 2 or 3). When the results of the job come in, I should see
Custom PSModulePath. This is the behavior in 5.1.Actual behavior
It takes between 12 and 20 seconds. That's longer than a second per job! (and I'm not waiting for the job to finish; this is just the time for
Start-Jobto return) And then the output is the default module path.Environment data