Skip to content

Conversation

@pavelsavara
Copy link
Member

interp reporting directly to chrome dev tools via performance.measure()

Contributes to #76316

@pavelsavara pavelsavara added this to the 8.0.0 milestone Oct 18, 2022
@pavelsavara pavelsavara self-assigned this Oct 18, 2022
@ghost
Copy link

ghost commented Oct 18, 2022

Tagging subscribers to 'arch-wasm': @lewing
See info in area-owners.md if you want to be subscribed.

Issue Details

interp reporting directly to chrome dev tools via performance.measure()

Contributes to #76316

Author: pavelsavara
Assignees: pavelsavara
Labels:

arch-wasm, area-System.Runtime.InteropServices.JavaScript

Milestone: 8.0.0

@pavelsavara
Copy link
Member Author

image

@pavelsavara
Copy link
Member Author

I just understood that src\mono\mono\profiler\aot.c is just plugin into src\mono\mono\metadata\profiler-private.h and it also works in wasm.

So I could use the same technique to do the browser integration.

mono_profiler_get_call_instrumentation_flags is what drives this

@pavelsavara
Copy link
Member Author

Closed in favor of #77449

@ghost ghost locked as resolved and limited conversation to collaborators Nov 25, 2022
@pavelsavara pavelsavara deleted the wasm_perf_measure branch September 2, 2024 15:28
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants