Latency on first execution of OCL functions
I´ve seen that there is a large latency, 0.6s, on the first call to OCL functions, and assume this is due to the function being uploaded and initialised. What is the persistency of functions once used? Can they be loaded for permanent readiness?
Are there any docs on this topic?
There were some topics here in the forum about the matter. Some users did experiments with usual functions, maybe you can find them if you dig enough. I don't think there are nay official docs though
Great :| OCL has been around years and this isn't yet covered?! its sort of hard to believe. Experiments? This should just be documented, the load program function must have some details, I'm guessing that once loaded a program stays resident until deleted... is there really no specs on this?
Okay, so I´ve read this https://www.khronos.org/registry/cl/s... it indicated that the latency is that on first load the program has to be compiled, but that the binary can be downloaded and stored for later use, avoiding the compilation delay, which is useful, although the page does not give a link to the functions to download the compiled binary as far as I can see.