Slow event triggering wien compared with krabsetw

[DavidXanatos]

I was testing the EventTracing from perfview and noticed that an event takes about 2.3 sec to be triggered using this library, in comparison https://github.com/microsoft/krabsetw only needs about 1 second.

is there a way to improve the latency of this library?

[sharwell]

We would need to see the specific scenario to identify the differences leading to this latency.

[DavidXanatos]

In my scenario I was watching the "Microsoft-Windows-Winsock-NameResolution" ProviderID: {55404E71-4DB9-4DEB-A5F5-8F86E46DDE56} And using a console tool that uses the NameResolution API to trigger these events, ping.exe or telnet.exe seam to be fine for that.

I noticed that a test application using the libray from perfview from when I caused an event to it being logged to the console it took over 2 seconds, while my actual application https://github.com/DavidXanatos/priv10 which is using currently the krabsetw library logs the events in 1 second.

I would like to switch to your library as it is fully .NET while krabsetw is at its core C++ those its not architecture independent. And I would like my tool to also work on ARM based hardware without the need for me to cross-compiling the krabsetw library for every conceivable architecture out there.

[github-actions[bot]]

Due to lack of recent activity, this issue has been labeled as 'stale'. It will be closed if no further activity occurs within 30 more days. Any new comment will remove the label.