Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Log gateway resolution times #759

Open
autonome opened this issue Sep 13, 2019 · 1 comment
Open

Log gateway resolution times #759

autonome opened this issue Sep 13, 2019 · 1 comment
Labels
kind/enhancement A net-new feature or improvement to an existing feature

Comments

@autonome
Copy link

Currently we're still experiencing very long times for loading content from gateway.

Companion has a unique view - it can see from the user POV when an IPFS URL is entered, to the time the content is finally loaded.

We should log these, even if not expose in UI anywhere, so that we can view for development purposes how it changes over time.

This could be a log, or even be a simple median load time for all gateway requests might be interesting.

Eventually if we had metrics to Companion, we could report this info for an anonymized view of gateway performance across all installs.

@lidel lidel added the kind/enhancement A net-new feature or improvement to an existing feature label Sep 13, 2019
@lidel
Copy link
Member

lidel commented Sep 13, 2019

What metrics would be useful to track?
While webRequest API still exists (#666 😈), it provides hooks for different stages of each request:

I am worried about logging every IPFS URL, but we could start with gathering content-agnostic data:

  • Gateway URL (just Origin, no path) + Content-Length + time between each stage
    • Content-Length should help us normalize time against the size of requested data

Thoughts? Anything to add?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/enhancement A net-new feature or improvement to an existing feature
Projects
No open projects
Status: Needs Grooming
Development

No branches or pull requests

2 participants