Handle's Kernel timing API is awkward and error-prone to use.

[amberhassaan]

Root of the awkwardness is that there is no field for accumulated kernel time in the Handle. Calling Run() automatically captures the kernel invocation time, but overwrites what was there. This means, the user has to often save the previous accumulated time, then run a kernel and then call AccumKernelTime() to accumulate kernel times.

This needs to be straightened out by adding a field for accumulated time so that the user does not have to worry about this careful orchestration.

Proposal: Add new field for accumulated time where time is accumulated automatically after each Run() call. GetKernelTime() now is replaced by GetLaskKernelTime() and GetAccumulatedKernelTime(). Also, ResetKernelTime() resets both the fields or just resetting the accumulated time field should be enough.

[atamazov]

[Informative] How to use old awkward API: #2429 (comment)

[JehandadKhan]

Instead of an issue, this should be part of the wiki.

…

On Tue, Feb 27, 2024 at 7:09 AM Artem Tamazov ***@***.***> wrote: [Informative] How to use old awkward API: #2429 (comment) <#2429 (comment)> — Reply to this email directly, view it on GitHub <#2736 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABK5ZOJC2CFDRX6AN37KQKLYVXLIXAVCNFSM6AAAAABC725CA2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNRWGUYTEOJQGA> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[amberhassaan]

My goal was to fix this awkwardness instead of documenting it.