LC job performance vs omconfig for changing disk controller write policy

Hello, I would like to not use OMSA (omreport/omconfig) because it seems it will go away in the future due to agent less monitoring and because it relies on the dcstor32/dcstro64 service to be running. I favor racadm and WSMAN to the idrac over omconfig.

However, the performance of some commands using LC Jobs is bad. For example, setting the disk controller vdisk write policy. Omconfig takes less than a second and the LC job after creation takes ~2 mins.

(In powershell using local racadm)

Omconfig:

PS C:\> (measure-command {$out = omconfig storage vdisk action=changepolicy vdisk=0 controller=0 writepolicy=fwb}).totalseconds;$out
0.8145142
Command successful!

LC Job:

PS C:\> racadm jobqueue delete --all

PS C:\> racadm set Storage.VirtualDisk.WritePolicy.1 'Force Write Back'

PS C:\> get-date;racadm jobqueue create RAID.Integrated.1-1 -s TIME_NOW --realtime;do{get-date;$out=racadm jobqueue view;$out;sleep -Seconds 5}while ([string]::IsNullOrEmpty($($out | select-string -SimpleMatch "[100]")));get-date