...
- From the early days of JobScheduler the distinction between Shell jobs and API jobs was introduced:
- Shell jobs include whatever can be executed from the command line of the respective shell (Unix or Windows)
- API jobs are coded in a programming/scripting language. JobScheduler exposes its API to supported languages.
- With PowerShell jobs such differences are leveled in a way that PowerShell jobs can include
- commands such as
- any calls to Windows commands and programs
- any PowerShell cmdlets
- any calls to .NET classes
- callch as
spooler_process()for
- commands such as
- At the time of writing a performance penalty is obseved for PowerShell jobs due to loading the .NET Framework PowerShell run-tme.
- The delay for PowerShell jobs starting compared to Shell job is about 1-2s. The effective delay depends on the users system performance.
- This delay corresponds more or less to the time required to execute PowerShell.exe from the command line.
...