Difference between revisions of "Performance & Benchmark"
Line 13: | Line 13: | ||
|style="font-size:85%;"| | |style="font-size:85%;"| | ||
<tabs> | <tabs> | ||
<!-- Xavier NX Starts --> | <!-- Xavier NX Starts --> | ||
<tab name="Xavier NX"> | <tab name="Xavier NX"> | ||
Line 149: | Line 147: | ||
</tab> | </tab> | ||
<!-- Xavier NX Ends--> | <!-- Xavier NX Ends--> | ||
<!-- RTX 2060 Starts --> | <!-- RTX 2060 Starts --> | ||
<tab name="RTX 2060"> | <tab name="RTX 2060"> | ||
Line 289: | Line 281: | ||
</tab> | </tab> | ||
<!-- RTX 2060 Ends--> | <!-- RTX 2060 Ends--> | ||
</tabs> | </tabs> | ||
|} | |} |
Revision as of 20:21, 25 October 2022
If one thing CUVI gives you, it's performance boost over competitive libraries and solutions. Using GPGPU as the underlying hardware, Imaging and Vision modules get maximum benefit due to their inherent parallel algorithms. In addition to cost cutting on CPU-based clusters, CUVI gives up to 15x speedup over Intel IPP.
Applications using CUVI are generally ten times faster than their CPU counterpart. CUVI framework also gives the ease to scale the application on more than one GPU making it as fast as you want.
Benchmark
The following benchmark via NVIDIA's Performance tools for Windows and Linux. Timing figure represents frames per second (rounded) based on only the processing time on the single GPU. The benchmarks are performed on color 8-bit per channel images except where mentioned otherwise.
|