awesome-software-patreons VS pyroscope

A list of awesome individual programmers and OSS projects looking for funding collected by on GitHub: https://github.com/uraimo/awesome-software-patreons opensource

There is this.

You might want to add those to https://github.com/uraimo/awesome-software-patreons/

There have been countless FOSS-centric bounty sites since the late 1990s. They never took off in a significant way and now people are using subscription-based platforms like Patreon and Liberapay: https://github.com/uraimo/awesome-software-patreons/

I guess in hindsight one could say that bounties are too messy while a subscription-based approach is much clearer (less managing overhead etc.).

Quoting from https://wiki.snowdrift.coop/market-research/history/software

"Many bounty sites have been tried over many years. Some sites that have come and gone: The Free Software Bazaar, CoSource, Fundry, Public Software Fund, BountyOSS, BitKick, COFundOS (which alled users to place bounties for new applications as well as for changes to existing programs), Opensourcexperts.com, Donorge, Bountycounty, Bounty Hacker, microPledge, FundHub (some unrelated site uses that name now, not surprisingly), GitBo, Catincan, DemandRush, and Open Funding (broken though the main domain openinitiative.com still exists) — and probably others we never discovered. GNOME and Launchpad each made attempts at supporting bounties but that never came to anything substantial. FOSS Factory (which is still live but has had no activity for years) bothered writing their own essay on the history of other failed bounty sites."

You might also want to check out https://wiki.snowdrift.coop/market-research/other-crowdfundi...

What do you mean? pyroscope.io was slow for you? or the blog?

Tries (or prefix trees).

We use them a lot at Pyroscope for compressing strings that have common prefixes. They are also used in databases (e.g indexes in Mongo) or file formats (e.g debug symbols in macOS/iOS Mach-O format are compressed using tries).

We have an article with some animations that go into details about tries in case anyone's interested [0].

[0] https://github.com/pyroscope-io/pyroscope/blob/main/docs/sto...

You could use continuous profiling with Pyroscope which uses async-profiler under the hood, but with the added functionality that you can add relevant tags to your VMs (example).

Java Flight Recorder (JFR) is a format for collecting diagnostic and profiling data from Java applications. A while back someone created an issue for Pyroscope , an open source continuous profiler written in Go, to support ingesting profiles in JFR format, but there were no existing parsers that were also written in Go.

This cloud version is actually a slimmed-down version of Pyroscope which is open source and so you can run it locally.

At Pyroscope (open source continuous profiling) we use flamegraphs extensively to visualize and analyze profiling data. However, one of the worst parts about using flamegraphs for analysis is that they are kind of annoying to share.