Cannot collect full trace of an OpenCL application

[TrimHG]

I tried to use Radeon Profiler and Radeon Developer panel to collect OpenCL application timeline trace, but could not get the tools to capture the whole trace of my application's OpenCL calls (it takes a couple of seconds for the application to run). I could only get the first ~50ms of trace since the application starts (rgp file is about 3.7 MB in size).

Any way to capture the whole timeline using Radeon Developer Tool Suite?

Changing dispatch range to 0-1000 does not help to capture more data.

[jpola-amd]

Hi, I have similar issue. With the OpenCL application I'm not able to collect one full profile (500s). Instead I'm able only to trigger several "short bursts".

I'm using latest version: RadeonDeveloperToolSuite-2020-11-19-376

I also manipulated the dispatch range. But it didn't help.

Is there any way to collect full profile.

Thanks.

[MarkIngramUK]

There's definite problems with the OpenCL capture, I have the profiler set to capture the maximum 1000 dispatches, and instead, I can only see 68 calls in the event list. Our own log files show around 4000 OpenCL calls (clEnqueueFillBuffer, clEnqueueNDRangeKernel, clEnqueueCopyBuffer, etc) per benchmark, so I can't work out why the profiler is cutting it short.

On top of that, the limit of 1000 (even if that worked) wouldn't be enough for us, I would like to see a ten-fold increase as a minimum.

[TrimHG]

Not yet addressed as of RD Panel v2.3.0.31, Radeon GPU Profiler v1.10.0.23.

[eladmaimoni]

I too am having no success with capturing OpenCL captures for a simple console application that enqueues a single kernel.