2016-10-06 09:16:19 -0600 | commented question | OpenCL latency at first call That answer is about sharing memory (image data) between process which both utilize the same GPU. For me, I only need to utilize the same OpenCL context, not the memory. |
2016-10-06 07:11:41 -0600 | commented question | OpenCL latency at first call Unfortunately not, the data will arrive irregularly and the program will be called on demand |
2016-10-06 04:17:32 -0600 | commented question | OpenCL latency at first call My hardware: i7-4710MQ, 8GB ram, Intel HD Graphics 4600 & AMD Firepro M6100, Win10 x64 |
2016-10-06 04:17:32 -0600 | asked a question | OpenCL latency at first call When using OpenCL in OpenCV 3.1 (so using UMat instead of Mat), I observe significant latency in the first call of a function. The project I am working on has some performance demands and will be ran in independent processes on the same machine with the same filters/settings (only the input image will change). I am using OpenCV 3.1 in VS2015. For example: This will give the following result: I checked whether OpenCL was enabled using This issue was already addressed in this question and this one but not yet solved. One of the causes of this latency could be the initialization of the OpenCL runtime at the first call. Is it possible to save the initialized state of OpenCL to file at the first run of my program and load it for consecutive runs? I know the ocl-module has classes like Program, ProgramSource and Context. However, I am not familiar with OpenCL in general and the documentations on these classes and how to use its members is nowhere to be found. |