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
We currently craft links to bb-portal where the user can download the profile for an invocation. This is a little dirty for, at least, two reasons. For one, the format of bb-portal links is not considered public API. And second, from bb-portal we have no control over how long the profile is persisted. It also requires the user to get the profile, and load it into e.g. chrome://tracing in order to view, which is cumbersome.
There are two improvements I'd like to see here. For one, we should persist the profile for any invocation in our own storage, and allow users to define as part of their bb-portal configuration how this is stored. And we should visualize the trace inside bb-portal itself. It's a relatively simple format, and there are libraries available for visualizing a flame graph, so this should be fairly straight forward.
The text was updated successfully, but these errors were encountered:
So I was talking with our devex team about this the other day and one of them had a good suggestion that we should provide a button that would allow you to persist this artifact further. So something like if you click on the button it saves it for X # of days, which I thought was a good compromise to serializing every one of these.
As for the flame graph visualization, i think we can certainly do something like this, but I don't think we can match the functionality provided by chrome's embedded tracing tool. Its fast, you can really zoom in and navigate around, it can handle tons of depth and complexity, etc. Even if we do surface a visualization in the UI for this data i think we should keep a way to download the item to your local machine.
We currently craft links to bb-portal where the user can download the profile for an invocation. This is a little dirty for, at least, two reasons. For one, the format of bb-portal links is not considered public API. And second, from bb-portal we have no control over how long the profile is persisted. It also requires the user to get the profile, and load it into e.g. chrome://tracing in order to view, which is cumbersome.
There are two improvements I'd like to see here. For one, we should persist the profile for any invocation in our own storage, and allow users to define as part of their bb-portal configuration how this is stored. And we should visualize the trace inside bb-portal itself. It's a relatively simple format, and there are libraries available for visualizing a flame graph, so this should be fairly straight forward.
The text was updated successfully, but these errors were encountered: