You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm developing an internal tool to capture performance data and generate flame graph SVGs. This tool aims to replace a set of scripts with a single executable featuring user-friendly sub-commands. The inferno library is working great, and I appreciate your effort in creating it! However, the coloring scheme of the produced SVGs differs from the original flamegraph.pl script, which has led to complaints from colleagues accustomed to the previous color scheme.
What do you think about one of this?
modify the library to match the original flamegraph.pl coloring scheme. This would ensure consistency with the color scheme familiar to existing users.
introduce an additional Palette option that can be used to replicate the original flamegraph.pl color scheme. This would provide flexibility for users who prefer the original color scheme while preserving the current default scheme.
The text was updated successfully, but these errors were encountered:
I'm interested to hear in what way it diverges — in general, this was a pretty direct port, including the color selection. It may however be that we've iterated further beyond the original flamegraph since then. Could you post some images of the differences?
Overall I'd be happy to include a palette that replicates the original 👍
I'm developing an internal tool to capture performance data and generate flame graph SVGs. This tool aims to replace a set of scripts with a single executable featuring user-friendly sub-commands. The inferno library is working great, and I appreciate your effort in creating it! However, the coloring scheme of the produced SVGs differs from the original flamegraph.pl script, which has led to complaints from colleagues accustomed to the previous color scheme.
What do you think about one of this?
The text was updated successfully, but these errors were encountered: