Append tag name to parallel construct name for Profiling

[ibaned]

carry-over kokkos/kokkos-tools#14

@stanmoore1

[ibaned]

Not sure how feasible this is yet, but conceptually it makes sense

[crtrott]

Its something we could do. Need to check how much launch latency it adds. But basically we use already typeid(functor).name() as default label, and we can simply append it with typeid(policy_type::tag_type).name() or so.

[stanmoore1]

If the launch latency is high, then could you only enable it when profiling is also enabled?

[ibaned]

@stanmoore1 I think thats already the case for the existing code that queries the typeid, anything we add inside that #ifdef block would similarly be protected.

[nmhamster]

The issue here is that we want to have profiling be enabled by default. We may end up with some functions for profiling disabled if they affect performance but the premise is "always available profiling". We can talk offline as to why this is important.

[ibaned]

I created PR #846, which I think will do what you want. I guess we could do some kind of performance testing with LAMMPS to see how it affects latency ?

[crtrott]

I think it should be ok. That said, all pull requests are on hold until:
(i) integration is done
(ii) Dan (Sunderlands) stuff is in.

[ibaned]

The changes are in develop

[stanmoore1]

@ibaned thanks!

[stanmoore1]

Just wanted to say thanks again for this enhancement, it makes profiling my code a lot easier