pyroscope
pyroscope copied to clipboard
grafana
Continuous Profiling Platform. Debug performance issues down to a single line of code
Currently the adhoc drag and drop has a lot of text and just looks generally messy.  We should copy the design from flamegraph.com and make it look closer to...
Point of having colors per package is to be able to easily distinguish what package a stacktrace belongs to. But apparently either there's an error with the hash calculation, or...
As of right now its kind of difficult to remove tags. I think there are a series of improvements we can make to tags to accomplish two goals: 1. make...
The idea was suggested by @korniltsev: > Let's say I have a big profile tree and I need to dig deeper to find usefull bits I chose node A, B,...
As the screenshot shows, it's important to be able to see the entire app name.
Works with updated `@pyroscope/nodejs` module https://github.com/pyroscope-io/pyroscope-nodejs/pull/19
Our current eBPF support can be improved in some areas, including: - It's built on top of (python) bcc tools, which is thus a dependency. - It periodically loads /...
### Problem Pyroscope uses [badger](https://github.com/dgraph-io/badger) which is a key-value database. It has good performance but it is operationally harder to use because it requires you to have a disk. It...
Example: https://user-images.githubusercontent.com/6951209/180288406-71cac256-339c-480e-9c42-e1ee9a194876.mp4
For some reason we debounce all inputs, which makes automated tests very unreliable. We should instead have 2 different kinds of inputs: `DebouncedInput` and `Input` instead. https://github.com/pyroscope-io/pyroscope/blob/main/webapp/javascript/ui/Input.tsx#L35