Changes in examples-profiling.md

310e6677 - Reorder book-based documentation (#8130)

Thu, 14 Mar 2024 17:41:27 +0000

Reorder book-based documentation (#8130)On a high level, this is what this PR changed:1. Move the CLI chapter before the API chapter. I think this makes sense because the CLI is more high-level. The same change was proposed in https://github.com/bytecodealliance/wasmtime/pull/7987.1. Move some Rust and C examples from the "Examples" chapter into the API chapter.1. Remove the original main C and Rust chapter introduction files. They contained mostly outdated or duplicate information.1. Rename the "Examples" chapter to "Further Examples". (For lack of a better name.)1. Rename "Embedding" to "API" at some places since API is a more generally known term. The term "embedding" is also slightly more confusing, I think, because the term nowadays also used a lot in LLM-related communication.1. Read through the entire document and fix some outdated links and information.1. Fix a missing subheading for Elixir (it was mentioned on the lang page, but not in the menu). List of files: /wasmtime-44.0.1/docs/examples-profiling.md

1b99b1fa - Basic guest-profiler documentation for the book (#6393)

Wed, 17 May 2023 22:25:02 +0000

Basic guest-profiler documentation for the book (#6393)* Basic guest-profiler documentation for the book* Review comments List of files: /wasmtime-44.0.1/docs/examples-profiling.md

c183e93b - x64: enable VTune support by default (#3821)

Tue, 22 Feb 2022 16:32:09 +0000

x64: enable VTune support by default (#3821)* x64: enable VTune support by default After significant work in the `ittapi-rs` crate, this dependency should build without issue on Wasmtime's supported operating systems: Windows, Linux, and macOS. The difference in the release binary is <20KB, so this change makes `vtune` a default build feature. This change upgrades `ittapi-rs` to v0.2.0 and updates the documentation. * review: add configuration for defaults in more places * review: remove OS conditional compilation, add architecture * review: do not default vtune feature in wasmtime-jit List of files: /wasmtime-44.0.1/docs/examples-profiling.md

dff789c7 - Adds JIT profiling support for VTune (#819)

Thu, 02 Apr 2020 14:04:08 +0000

Adds JIT profiling support for VTune (#819)This patch adds initial support for ittapi which is an open source profiling api for instrumentation and tracing and profiling of jitted code. Result files can be read by VTune for analysis Build: cargo build --features=vtune Profile: // Using amplxe-cl from VTune amplxe-cl -v -collect hostpost target/debug/wasmtime --vtune test.wasm List of files: /wasmtime-44.0.1/docs/examples-profiling.md

00200504 - correct typo in the docs profiling section (#1442)

Tue, 31 Mar 2020 14:22:56 +0000

correct typo in the docs profiling section (#1442) List of files: /wasmtime-44.0.1/docs/examples-profiling.md

adff4327 - Fix build of the book (#1368)

Fri, 20 Mar 2020 17:18:57 +0000

Fix build of the book (#1368) List of files: /wasmtime-44.0.1/docs/examples-profiling.md

3b7cb6ee - Enable jitdump profiling support by default (#1310)

Fri, 20 Mar 2020 16:44:51 +0000

Enable jitdump profiling support by default (#1310)* Enable jitdump profiling support by default This the result of some of the investigation I was doing for #1017. I've done a number of refactorings here which culminated in a number of changes that all amount to what I think should result in jitdump support being enabled by default: * Pass in a list of finished functions instead of just a range to ensure that we're emitting jit dump data for a specific module rather than a whole `CodeMemory` which may have other modules. * Define `ProfilingStrategy` in the `wasmtime` crate to have everything locally-defined * Add support to the C API to enable profiling * Documentation added for profiling with jitdump to the book * Split out supported/unsupported files in `jitdump.rs` to avoid having lots of `#[cfg]`. * Make dependencies optional that are only used for `jitdump`. * Move initialization up-front to `JitDumpAgent::new()` instead of deferring it to the first module. * Pass around `Arc` instead of `Option>>>` The `jitdump` Cargo feature is now enabled by default which means that our published binaries, C API artifacts, and crates will support profiling at runtime by default. The support I don't think is fully fleshed out and working but I think it's probably in a good enough spot we can get users playing around with it! List of files: /wasmtime-44.0.1/docs/examples-profiling.md