Searched refs:profiling (Results 1 – 17 of 17) sorted by relevance
| /wasmtime-44.0.1/docs/ |
| H A D | examples-profiling.md | 6 bit deeper into the performance of your Wasm, and this is where profiling comes 12 Wasmtime to your platform's native profiling tools. 14 As a result, Wasmtime support for native profiling is limited to certain 18 - On Linux, we support [perf](./examples-profiling-perf.md). 21 [VTune](./examples-profiling-vtune.md). 23 - For Linux and macOS, we support [samply](./examples-profiling-samply.md). 26 profiler](./examples-profiling-guest.md).
|
| H A D | examples-profiling-vtune.md | 3 [VTune][main] is a popular performance profiling tool that targets both 32-bit 4 and 64-bit x86 architectures. The tool collects profiling data during runtime 11 VTune support in Wasmtime is provided through the JIT profiling APIs from the 31 For JIT profiling with VTune, Wasmtime currently builds with the `vtune` feature 37 `ProfilingStrategy::VTune` to enable profiling of your wasm modules. 47 Note that VTune is capable of profiling a single process or all system 48 processes. Like `perf`, VTune is capable of profiling the Wasmtime runtime 65 profiling data as Wasmtime is executing `foo.wasm`. The `--profile=vtune` flag enables 68 command is a results directory `r000hs/` which contains profiling data for 101 path. To collect hot spot profiling information, we execute:
|
| H A D | SUMMARY.md | 29 - [Profiling WebAssembly](./examples-profiling.md) 30 - [Profiling with Perf](./examples-profiling-perf.md) 31 - [Profiling with VTune](./examples-profiling-vtune.md) 32 - [Profiling with `samply`](./examples-profiling-samply.md) 33 - [Cross-platform Profiling](./examples-profiling-guest.md)
|
| H A D | examples-profiling-guest.md | 3 The guest profiling strategy enables in-process sampling and will write the 14 multiple of the profiling interval.
|
| H A D | examples-profiling-samply.md | 9 Simple profiling support with `samply` generates a "perfmap" file that the `samply` CLI will 11 Wasmtime itself, so you will need to manually change a few things to enable profiling support in 15 `ProfilingStrategy::PerfMap` to enable profiling of your wasm modules.
|
| H A D | examples-profiling-perf.md | 9 There are two profiling agents for `perf`: 17 Simple profiling support with `perf` generates a "perf map" file that the `perf` CLI will 19 Wasmtime itself, so you will need to manually change a few things to enable profiling support in 23 `ProfilingStrategy::PerfMap` to enable profiling of your wasm modules. 64 change a few things to enable profiling support in your application. First 70 `ProfilingStrategy::JitDump` to enable profiling of your wasm modules.
|
| H A D | examples-pulley.md | 199 * When profiling the "match loop" it's not clear what machine code corresponds 203 * When profiling with the "tail loop" you can see hot opcodes much more clearly, 208 instruction-level profiling in `perf` it can be useful to look at opcode-level 209 profiling of Pulley. 211 Pulley has limited support for opcode-level profiling. This is off-by-default as 236 Some more information can be found in [the PR that implemented Pulley profiling
|
| H A D | contributing-architecture.md | 515 * `wasmtime-profiling` - implementation of hooking up generated JIT code to 516 standard profiling runtimes.
|
| /wasmtime-44.0.1/crates/c-api/artifact/ |
| H A D | Cargo.toml | 26 'profiling', 51 profiling = ["wasmtime-c-api/profiling"]
|
| /wasmtime-44.0.1/crates/wasmtime/src/ |
| H A D | runtime.rs | 118 mod profiling; module 120 pub use profiling::GuestProfiler;
|
| /wasmtime-44.0.1/crates/c-api/ |
| H A D | Cargo.toml | 47 profiling = ["wasmtime/profiling"]
|
| /wasmtime-44.0.1/crates/c-api/src/ |
| H A D | lib.rs | 32 mod profiling; module
|
| /wasmtime-44.0.1/crates/c-api/cmake/ |
| H A D | features.cmake | 29 feature(profiling ON)
|
| /wasmtime-44.0.1/tests/all/ |
| H A D | main.rs | 49 mod profiling; module
|
| /wasmtime-44.0.1/crates/wasmtime/ |
| H A D | Cargo.toml | 140 'profiling', 190 # Enables support for profiling guest modules. 191 profiling = [ 403 # performance hit, even when not profiling, so it's disabled by default at 407 "profiling",
|
| /wasmtime-44.0.1/ |
| H A D | Cargo.toml | 498 "profiling", 574 profiling = ["wasmtime/profiling", "wasmtime/call-hook"] 702 [profile.profiling]
|
| /wasmtime-44.0.1/.github/workflows/ |
| H A D | main.yml | 338 -p wasmtime --no-default-features --features profiling
|