--
You received this message because you are subscribed to the Google Groups "aparapi-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to aparapi-discuss+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Hi jnelson,
Actually, it's no longer so bad as Gary suggests, if you are using the current build from GitHub.
Due to multiple contributions (some of them mine;) most of the
old overheads of Kernel instantiation are now no longer a factor.
In the latest repository version, all of the reflection, bytecode
analysis, CL generation and CL compilation and so on are cached
(even the compiled binaries are cached on the JNI side).
It is still the case that for maximum optimality you should reuse
Kernel instances, but you will probably find that in the latest
development build it doesn't make a great deal of difference.
Barney
To unsubscribe from this group and stop receiving emails from it, send an email to aparapi-discu...@googlegroups.com.
To unsubscribe from this group and stop receiving emails from it, send an email to aparapi-discu...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
In my (principal) application it is very difficult to reuse
Kernels, multiple threads might need access to a given Kernel type
simultaneously (prompting me to contribute some of the changes
referred to). In a client-server scenario such as mine things can
get quite difficult quite quickly. I think that if it is practical
to create one Kernel and reuse it, you should do so, but would be
very interested to see the results of any comparisons you might
perform.
Thanks, but wasn't just me! I applied some C++ code from Jaeju
Kim and I think it was Ryan LaMothe who did some of the earliest
caching stuff.
To unsubscribe from this group and stop receiving emails from it, send an email to aparapi-discu...@googlegroups.com.
Jared,
I guess this prompts the question, "when will the current dev build be put live"?
I have no idea who would be responsible for such an action, now that Gary no longer works for AMD.
Barney
To unsubscribe from this group and stop receiving emails from it, send an email to aparapi-discu...@googlegroups.com.
--
Hi
We *really* need automated builds back working, not to mention better build scripts. It's definitely something which needs addressing, took me several hours to figure out how to originally build on Windows (I've not tried Linux) and to get it working required a lot of tampering with scripts (not just property files).
However, it should be possible to debug into a pure-java implementation with the binary release you have, it just uses a different (per-Kernel) mechanism. If I recall correctly, the code is
kernel.setExecutionMode(EXECUTION_MODE.JTP);
That will cause the code to be invoked on a Java
ThreadPoolExecutor.
EXECUTION_MODE.SEQ would run it in a single thread, obviously easier for debugging, but I seem to recall it is broken in the current non-development release. Give EXECUTION_MODE.SEQ a try, if it fails then you'll have to use EXECUTION_MODE.JTP.
Barney.