Hi, > I still have some polishing to do for the autotuner, so that it indeed > print the same thing as viennacl-info. The problem of the MIC is that I > have aaaaabsolutely ZERO idea of how to prune profiles. We can try, with > the GPU configuration so that it remains tractable, but I don't > guarantee any good result :P
It's still questionable whether the current OpenCL SDK for MIC is able to provide any performance at all... > Nice for the K20X :) I still have to work out things though, to make > sure #pragma unroll is always called on NVidia Hardware, and never > called on AMD hardware... Performing an extensive search just creates so > many constraints. > I'll send an update when I consider the autotuner is ready for the K20X > and the MIC... Good, I'll arrange things on the K20X machine in the meanwhile... > We should document this, yes. However, I don't know whether we can > reliably warn about this. It may even be driver or OS dependent. > > > Hmm, true that I should pass this specific benchmark to codeXL, to know > where the bad performance comes from. My guess for now is that it comes > from channel conflict... That must be more than just a conflict - a full channel war ;-) > Do you still plan to make a GUI for the Autotuner. I'm realizing that > this could be a really nice feature, since it allows one to freely > choose the parameter space ... Yes, I do! I'll write it right after the 1.5.0 release. Best regards, Karli ------------------------------------------------------------------------------ Get 100% visibility into Java/.NET code with AppDynamics Lite! It's a free troubleshooting tool designed for production. Get down to code-level detail for bottlenecks, with <2% overhead. Download for free and get started troubleshooting in minutes. http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk _______________________________________________ ViennaCL-devel mailing list ViennaCL-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/viennacl-devel
