On Montag 10 Mai 2010, tmp wrote: > I experience some very odd behavior from either pyopencl or opencl. I have > produced a boiled-down example and posted it below. Basically the test > kernel below takes some large arrays as arguments and initializes one of > these with 1's. It also performs a for-loop in which it initializes some > local data structures with 1's and does nothing else. In theory this > for-loop could be omitted as it does nothing relevant to the output, > but... The strange thing is, that when the for-loop has many iterations > (e.g. 1000), things goes horribly wrong, the screen flickers, and the > output array is not initialized with 1's. If the loop only has a few > iterations (e.g. 10), everything works fine. Also, if the variable "rows" > in the outer python code is lowered to e.g. 144 instead of 3344, it also > works fine, even with 1000 for-iterations. > > Can anyone explain what is going on here?! > (The code takes around 14 seconds to complete on my laptop)
On Nvidia hardware that is also used for display, there is a hard limit of 5 seconds of kernel execution time. After that, the kernel is aborted and an error returned. You will likely need to split up that kernel into multiple smaller ones. HTH, Andreas
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ PyOpenCL mailing list [email protected] http://lists.tiker.net/listinfo/pyopencl
