-------- Original Message --------
Michael & Olivier, The JavaCL-Bridj preview is out. Having already written a benchmark with timings preserved on a webpage, it was logical to revisit this. There is no-longer a low level bindings, so I changed it to JavaCL proper. If I compare the old OpenCL4Java code with the new Bridj version I get a 66.5% reduction. My problem is when I compare the absolute timings to those on the web page, the base line is now 3x larger, so the reduction just puts JavaCL back where is was. I am finding this a little hard to understand. I could almost put it down to I am now running 257.21, but back in early March 196.xxx. The ICD could also be different. If I look closely at my first post however, I say my avg. MS per loop is from my Mac, but in the rules I give nVidia version #'s. I re-ran the original code on OSX with beta4 OpenCL4Java, and I get a 2.5x increase. Even here the date on the OpenCL "DLL" is now 06/10/10. I do not know how I got a file that new. Trying to keep my sanity, I thought I would just run the JOCL side. If it also was much higher, then just ignore the old data. Problem is I cannot get it to run. The source is missing an import, no biggie, but I built a NB library wt - jocl.jar - jocl-natives-windows-amd64.jar - jocl-natives-windows-i586.jar - gluegen-rt.jar I am getting an unSatisfiedLinkError: no jocl in java.library.path . What am I missing? Thanks, Jeff
yes you are right. Thanks for remembering me on this point. Its a trivial compile-time dependency which is only there for public-API convenience reasons. I'll update the script to allow compiling against jogl jars (automatic download etc) soon.
|Free forum by Nabble||Edit this page|