bytehound
tracing
Our great sponsors
bytehound | tracing | |
---|---|---|
16 | 52 | |
3,856 | 4,939 | |
- | 3.3% | |
3.8 | 7.8 | |
9 months ago | 2 days ago | |
C | Rust | |
GNU General Public License v3.0 or later | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
bytehound
-
My Rust program (Well, game) is leaking memory, 4MB/s.
I've found bytehound helpful for tracking memory leaks: https://github.com/koute/bytehound
-
Show HN: I wrote a tool in Rust for tracking all allocations in a Linux process
Interesting approach. How is performance compared to something like https://github.com/koute/bytehound
-
Introducing alloc-track: Precise memory profiling by stack trace and thread.
https://github.com/koute/bytehound is another tool in this space to be aware of
- Out of the loop: WASM for non-web projects
- Which gui crate would you suggest for a simple program?
-
Implementing a C++ memory allocator to track our framework memory usage
Ot sure if it will fit your needs but maybe bytehound is worth looking into.
-
Memory leak in a long running process.
I had a great success recently with https://github.com/koute/bytehound/issues/86
- Hi, I’m new in rust, I have some expirience with c# and its classes ans structs. I can’t find information about that is happend with struct in rust when I pass it to function argument. Are there some copy effect ?
- Does rust have a visual analysis tool for memory and performance like pprof of golang?
-
Memory freed but not immediately
Try using this: https://github.com/koute/bytehound
tracing
-
Decrusting the tracing crate [video] by Jon Gjengset
The video description is as follows:
In this stream, we peel back the crust on the tracing crate — https://github.com/tokio-rs/tracing/ — and explore its interface, structure, and mechanisms. We talk about spans, events, their attributes and fields, and how to think about them in async code. We also dig into what subscribers are, how they pick up events, and how you can construct your own subscribers through the layer abstraction. For more details about tracing, see https://docs.rs/tracing/latest/tracing/.
-
Vendor lock-in is in the small details
> What's been your biggest issues around ergonomics/amenities for OpenTelemetry?
I can't speak generally, but in the Rust ecosystem the various crates don't play well together. Here's one example: <https://github.com/tokio-rs/tracing/issues/2648> There are four crates involved (tracing-attributes, tracing-opentelemetry, opentelemetry, and opentelemetry-datadog) and none of them fit properly into any of the others.
-
Grimoire - A recipe management application.
The tracing (logging) mechanism in an asynchronous codebase (tracing).
-
How easy is it to swap out your async runtime?
Tracing is Tokio's alternative for async code.
-
Hey Rustaceans! Got a question? Ask here (27/2023)!
At a technical level, in Rust, both [tracing]https://crates.io/crates/tracing) and log are entire ecosystems (though for the latter at least there's also third party logging frameworks), and there's at least a bridge from log to tracing.
-
How can I write a tracing subscriber that saves to a database?
I am using https://github.com/tokio-rs/tracing for logging purposes in my application. I would like to develop a feature wherein logs should be saved to a database table (via sea-orm). Something similar is this, but it does not solve my needs fully.
-
A locking war story
I've used the tracing infrastructure with tracing_flame to profile some hot paths in async code: https://github.com/tokio-rs/tracing/tree/master/tracing-flame
-
I was wrong about rust
Oh nice! IIRC when I checked, it was the Unicode tables that smashed the code size. I recently hit the same issue with the tracing crate, where a crate feature (for env var filtering) pulled in regex and my binary was suddenly 1MB bigger.
-
Debugging and profiling embedded applications.
I know about tools such as tracing, jaeger or tracy. While having a complete tracing could be a potential solution, these tools don't work with no_std.
-
Custom Axum Logging for Routes?
tracing by itself only outputs log data, you need to consume them in a subscriber, the tracing-subscriber crate exists for this. (example)
What are some alternatives?
memory-profiler - A memory profiler for Linux. [Moved to: https://github.com/koute/bytehound]
log4rs - A highly configurable logging framework for Rust
heaptrack - A heap memory profiler for Linux
slog - Structured, contextual, extensible, composable logging for Rust
goawk - A POSIX-compliant AWK interpreter written in Go, with CSV support
env_logger - A logging implementation for `log` which is configured via an environment variable.
pprof - pprof is a tool for visualization and analysis of profiling data
log - Logging implementation for Rust
heappy - heap profiler for rust
opentelemetry-rust - The Rust OpenTelemetry implementation
pprof-rs - A Rust CPU profiler implemented with the help of backtrace-rs
vector - A high-performance observability data pipeline.