eakey

> Is it possible to use a more recent version of the sdk? No, I need to use the Windows 8.1 SDK because some client machines are still running on...

> Are you using the most recent 8.1 sdk? This error looks like a bug that I saw in the 10.x sdk If using Visual Studio 2022 (v143) and the...

> That doesn't answer my question? Maybe you are using an older version of the 8.1 sdk? How can I switch to the newer 8.1 SDK in this case? 

> I thought that the `8.1` would also have multiple version but apparently it doesn't. I do think you can switch to the most recent 10.x SDK. We are setting...

> That is correct and a limitation of the OpenCL library. It will always use all cores when running on CPU. We could add an extra check for this that...

> SetMagickResourceLimit(ThreadResource, 2) My application environment is restricted to using CPU-based OPENCL exclusively. Although an interface like SetMagickResourceLimit(ThreadResource, 2) is supposed to limit the number of CPU cores used, it...

> As I said before the api of the OpenCL library that is being used does not allow limiting the number of cores that are being used by an OpenCL...

> Don't forget that you are also getting a performance improvement because you are using all cores of the CPU. No, I am limited to using only 2 cores, and...

That's why I was considering if setting SetMagickResourceLimit(ThreadResource, 2) could also apply to OPENCL. I'm currently looking into how to limit CPU core usage within OPENCL. When OPENCL runs on...