Maybe this can help you: http://pastebin.com/raw.php?i=vPwFpVRt You mostly wait for event.wait()… Johannes Schönberger Am 27.05.2013 um 23:59 schrieb Stéfan van der Walt <stefan@sun.ac.za>:
On Mon, May 27, 2013 at 10:55 PM, Marc de Klerk <deklerkmc@gmail.com> wrote: The problem is this next graph…. Besides the difference between the c++ and the other two, there's still a large difference between the c++
Can you just explain again the difference between the two plots above?
Stéfan
-- You received this message because you are subscribed to the Google Groups "scikit-image" group. To unsubscribe from this group and stop receiving emails from it, send an email to scikit-image+unsubscribe@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Hi Johannes, Yeah I was thinking about that... The gpu code doesn't execute straight away - it's scheduled by the OpenCL implementation... So it usually just executes when the GPU is not busy doing it's usual rendering job. There''s not going to be any way to avoid the wait... I haven't had much experience with profiling c++ code like you did in the previous screenshot - could you tell me how to go about it? I think the matter is closed then. Thanks very much for the help! On Tuesday, May 28, 2013 8:00:03 AM UTC+2, Johannes Schönberger wrote:
Maybe this can help you: http://pastebin.com/raw.php?i=vPwFpVRt
You mostly wait for event.wait()…
Johannes Schönberger
Am 27.05.2013 um 23:59 schrieb Stéfan van der Walt <ste...@sun.ac.za<javascript:>>:
On Mon, May 27, 2013 at 10:55 PM, Marc de Klerk <dekl...@gmail.com<javascript:>> wrote: The problem is this next graph…. Besides the difference between the c++ and the other two, there's still a large difference between the c++
Can you just explain again the difference between the two plots above?
Stéfan
-- You received this message because you are subscribed to the Google Groups "scikit-image" group. To unsubscribe from this group and stop receiving emails from it, send an email to scikit-image...@googlegroups.com <javascript:>. For more options, visit https://groups.google.com/groups/opt_out.
I used the line_profiler package on the Python side, but for C/C++ debugging I recommend gdb / gprof / valgrind. Johannes Schönberger Am 28.05.2013 um 14:42 schrieb Marc de Klerk <deklerkmc@gmail.com>:
Hi Johannes,
Yeah I was thinking about that... The gpu code doesn't execute straight away - it's scheduled by the OpenCL implementation... So it usually just executes when the GPU is not busy doing it's usual rendering job. There''s not going to be any way to avoid the wait...
I haven't had much experience with profiling c++ code like you did in the previous screenshot - could you tell me how to go about it?
I think the matter is closed then. Thanks very much for the help!
On Tuesday, May 28, 2013 8:00:03 AM UTC+2, Johannes Schönberger wrote: Maybe this can help you: http://pastebin.com/raw.php?i=vPwFpVRt
You mostly wait for event.wait()…
Johannes Schönberger
Am 27.05.2013 um 23:59 schrieb Stéfan van der Walt <ste...@sun.ac.za>:
On Mon, May 27, 2013 at 10:55 PM, Marc de Klerk <dekl...@gmail.com> wrote: The problem is this next graph…. Besides the difference between the c++ and the other two, there's still a large difference between the c++
Can you just explain again the difference between the two plots above?
Stéfan
-- You received this message because you are subscribed to the Google Groups "scikit-image" group. To unsubscribe from this group and stop receiving emails from it, send an email to scikit-image...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
-- You received this message because you are subscribed to the Google Groups "scikit-image" group. To unsubscribe from this group and stop receiving emails from it, send an email to scikit-image+unsubscribe@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
On Tue, May 28, 2013 at 3:00 PM, Johannes Schönberger <jschoenberger@demuc.de> wrote:
I used the line_profiler package on the Python side, but for C/C++ debugging I recommend gdb / gprof / valgrind.
I usually combine Valgrind with kcachegrind--the visualization sometimes helps a lot. Stéfan
participants (3)
-
Johannes Schönberger -
Marc de Klerk -
Stéfan van der Walt