Activity

1. ghost added

   area-Tracing-coreclr

   on May 12, 2022
2. ghost added

   untriagedNew issue has not been triaged by the area ownerNew issue has not been triaged by the area owner

   on May 12, 2022
3. lambdageek

   added

   arch-wasmWebAssembly architectureWebAssembly architecture

   area-Tracing-mono

   and removed

   area-Tracing-coreclr

   on May 12, 2022
5. lambdageek

   added

   trackingThis issue is tracking the completion of other related issues.This issue is tracking the completion of other related issues.

   and removed

   untriagedNew issue has not been triaged by the area ownerNew issue has not been triaged by the area owner

   on May 12, 2022
6. lambdageek

   added this to the 7.0.0 milestone on May 19, 2022
7. lambdageek

   modified the milestones: 7.0.0, 8.0.0 on Aug 9, 2022
8. lambdageek

   modified the milestones: 8.0.0, 9.0.0 on Jul 12, 2023
9. tommcdon

   added

   enhancementProduct code improvement that does NOT require public API changes/additionsProduct code improvement that does NOT require public API changes/additions

   on Mar 12, 2024
10. lewing

    modified the milestones: 9.0.0, Future on Apr 26, 2024
11. pavelsavara

    modified the milestones: Future, 10.0.0 on Dec 12, 2024
12. pavelsavara

    self-assigned this

    on Dec 12, 2024
13. danroth27

    added

    Priority:0Work that we can't release withoutWork that we can't release without

    on Jan 13, 2025
14. javiercn

    added a sub-issue on Jan 23, 2025

    • Performance profiling for WebAssembly #76316
15. danroth27

    changed the title [-][wasm-ep] Tracking[/-] [+][wasm-ep] .NET WebAssembly profiling and memory diagnostics[/+] on Feb 5, 2025
16. pavelsavara

    changed the title [-][wasm-ep] .NET WebAssembly profiling and memory diagnostics[/-] [+][wasm] .NET WebAssembly profiling and memory diagnostics[/+] on Feb 10, 2025
17. pavelsavara commented on Feb 10, 2025

    

    pavelsavara

    on Feb 10, 2025

    Member

    More actions

    Previous goals

    • [wasm-ep] Minimal diagnostic tracing configuration and sample #69158
      This adds support for using the JS console to create an EventPipe session with the default providers and to collect a trace in-memory to the Emscripten VFS and to egress it to a JavaScript Blob object (which can then be downloaded).

    • [wasm-ep] Implement EventSource counters support; add an EventPipeSessionOptions builder to TS #69567

      • Add support for specifying the providers for a session.
      • Allow the EventSource counter polling thread to start.

    • Save runtime artifacts from the EventPIpe build in an ep subfolder in the runtime pack (in addition to mt and plain) (variant of [wasm-mt] place multi-threaded wasm build into separate artifacts folders #68506) we ended up with separate runtime packs selected using MonoWasmBuildVariant=perftrace or MonoWasmBuildVariant=multithread in Add support for building WASM variants alongside single-threaded to the build system #71054

    • SDK property to build the app with profiling enabled using the ep variant of the runtime artifacts The browser-wasm SDK should automatically reference the threading/perf-tracing ref assemblies #72872

    The goal is to make it possible to add "something" to a webassembly project in order to cause it to collect a nettrace file that can be fed to the dotnet-pgo tool to produce an .mibc file which can be consumed by the Mono AOT compiler.

    • [mono][eventpipe] Implementing MethodDetails and BulkType events #68571
    • [wasm-ep] Add a hook to start an EventPipe Session from runtime startup #69674
    • [wasm-ep] Implement DiagnosticServer and startup sessions for WebAssembly #72482
    • [wasm-ep] End-to-end workflow for profiled AOT using EventPIpe #72481
    • Diagnostic server support [wasm-ep] Implement DiagnosticServer and startup sessions for WebAssembly #72482
      The goal is to make it possible to start and stop EventPipe sessions using a dotnet-dsrouter and dotnet-counters/dotnet-trace/etc combo when running a dev server.
    • [dsrouter] Implement a WebSocket server diagnostics#3422 (prototype dotnet-dsrouter server-websocket is https://github.com/lambdageek/diagnostics/tree/wasm-server)
    • [wasm-ep] Configure the Diagnostic Server using DOTNET_DiagnosticPorts #73011
    • [wasm-ep] Can't have both runtime and EventSource event providers in the same session #69568
    • Performance profiling for WebAssembly #76316
18. pavelsavara commented on Feb 10, 2025

    

    pavelsavara

    on Feb 10, 2025

    Member

    More actions

    unified with #76316
19. pavelsavara

    closed this as completedon Feb 10, 2025
20. pavelsavara

    removed a sub-issue on Feb 10, 2025

    • Performance profiling for WebAssembly #76316
21. pavelsavara

    removed

    trackingThis issue is tracking the completion of other related issues.This issue is tracking the completion of other related issues.

    Priority:0Work that we can't release withoutWork that we can't release without

    on Feb 10, 2025
22. github-actions

    locked and limited conversation to collaborators on Mar 13, 2025