# Slow performance of VIC based rectification **URL:** \ **Category:** DRIVE AGX Orin General\ **Tags:** driveworks-image-processing\ **Created:** [June 28, 2026, 12:58pm UTC](https://forums.developer.nvidia.com/t/slow-performance-of-vic-based-rectification/374803 "2026-06-28T12:58:11Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![vladimir.tchernitski1](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@vladimir.tchernitski1](https://forums.developer.nvidia.com/u/vladimir.tchernitski1)\ **Post date:** [June 28, 2026, 12:58pm UTC](https://forums.developer.nvidia.com/t/slow-performance-of-vic-based-rectification/374803/1 "2026-06-28T12:58:11Z")
Continuing the discussion from [Rectification of supported Entron F008A120RM0AV2 Camera Sensor](https://forums.developer.nvidia.com/t/rectification-of-supported-entron-f008a120rm0av2-camera-sensor/316842): **DRIVE OS Version:** 6.0.8.1 **Issue Description:** I have exactly the same issue as author of referenced topic had. The only thing is that I was able to fix broken rectification results by cropping original input 3848x2168 to 3840x2160. The rectified image is okay now. My problem is VIC rectification performance is ~15Hz only for 3840x2160 resolution. Is it expected performance? ---
**Author:** ![SivaRamaKrishnaNV](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/sivaramakrishnanv/32/14043_2.png) [@SivaRamaKrishnaNV](https://forums.developer.nvidia.com/u/SivaRamaKrishnaNV)\ **Post date:** [June 29, 2026, 6:38am UTC](https://forums.developer.nvidia.com/t/slow-performance-of-vic-based-rectification/374803/4 "2026-06-29T06:38:21Z")
Dear @vladimir.tchernitski1 , Could you please share repro steps? did you use DW rectification sample with input video?Also, may I know is there any dependency on DOS 6.0.8.1 release? ---
**Author:** ![vladimir.tchernitski1](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@vladimir.tchernitski1](https://forums.developer.nvidia.com/u/vladimir.tchernitski1)\ **Post date:** [June 29, 2026, 11:57am UTC](https://forums.developer.nvidia.com/t/slow-performance-of-vic-based-rectification/374803/5 "2026-06-29T11:57:49Z")
Hello SivaRamaKrishnaNV, I just use rectifierLDC example and instead of default 1200x800 movie I used our own 3840x2160. I am going to profile the same scenario on DOS 6.0.10 but I was able to profile slow rectification on 6.0.8 I see that actual VIC processing takes 17.9ms that is closer to my expectation ~55Hz. But there is NvMediaLdcSetWarpMapParameters - 22.772 ms that happens completely on CPU just before VIC and taking 100% core. How to avoid it? ![Screenshot from 2026-06-29 14-47-49](https://global.discourse-cdn.com/nvidia/original/4X/4/a/f/4af789c37667eabdd92560eb3d1028e692e0e43b.png) ---
**Author:** ![SivaRamaKrishnaNV](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/sivaramakrishnanv/32/14043_2.png) [@SivaRamaKrishnaNV](https://forums.developer.nvidia.com/u/SivaRamaKrishnaNV)\ **Post date:** [June 29, 2026, 1:39pm UTC](https://forums.developer.nvidia.com/t/slow-performance-of-vic-based-rectification/374803/6 "2026-06-29T13:39:42Z")
> [@vladimir.tchernitski1](#): > > NvMediaLdcSetWarpMapParameters - 22.772 ms It does a memcpy type of operation, involves several memory access operations and expected to be slow with big images ---
**Author:** ![vladimir.tchernitski1](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@vladimir.tchernitski1](https://forums.developer.nvidia.com/u/vladimir.tchernitski1)\ **Post date:** [June 30, 2026, 6:41am UTC](https://forums.developer.nvidia.com/t/slow-performance-of-vic-based-rectification/374803/7 "2026-06-30T06:41:27Z")
Solved. Replaced dwRectifier\_warpNvMedia by “manual” flow. in init: NvMediaLdcSetWarpMapParameters(…) once, in frame loop - NvMediaLdcProcess(…) ---
**Author:** ![SivaRamaKrishnaNV](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/sivaramakrishnanv/32/14043_2.png) [@SivaRamaKrishnaNV](https://forums.developer.nvidia.com/u/SivaRamaKrishnaNV)\ **Post date:** [June 30, 2026, 6:51am UTC](https://forums.developer.nvidia.com/t/slow-performance-of-vic-based-rectification/374803/8 "2026-06-30T06:51:08Z")
Is NvMediaLdcSetWarpMapParameters called multiple times earlier and causing bottleneck? ---
**Author:** ![vladimir.tchernitski1](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@vladimir.tchernitski1](https://forums.developer.nvidia.com/u/vladimir.tchernitski1)\ **Post date:** [June 30, 2026, 6:55am UTC](https://forums.developer.nvidia.com/t/slow-performance-of-vic-based-rectification/374803/9 "2026-06-30T06:55:23Z")
Correct. Every dwRectifier\_warpNvMedia call leads to a call of NvMediaLdcSetWarpMapParameters internally (at least according to the profiler) ---
**Author:** ![SivaRamaKrishnaNV](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/sivaramakrishnanv/32/14043_2.png) [@SivaRamaKrishnaNV](https://forums.developer.nvidia.com/u/SivaRamaKrishnaNV)\ **Post date:** [June 30, 2026, 8:43am UTC](https://forums.developer.nvidia.com/t/slow-performance-of-vic-based-rectification/374803/10 "2026-06-30T08:43:46Z")
Thank you for update. ---
**Author:** ![system](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/system/32/68080_2.png) [@system](https://forums.developer.nvidia.com/u/system)\ **Post date:** [July 24, 2026, 5:47am UTC](https://forums.developer.nvidia.com/t/slow-performance-of-vic-based-rectification/374803/12 "2026-07-24T05:47:29Z")
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.