Skip to content
This repository has been archived by the owner on Jun 2, 2023. It is now read-only.

Add timing information to logs #31

Open
gajus opened this issue Mar 9, 2022 · 1 comment
Open

Add timing information to logs #31

gajus opened this issue Mar 9, 2022 · 1 comment
Labels
priority:low ❄️ This is a low priority task. Handle it when there is nothing else to do type:feature 🚀 Good for newcomers

Comments

@gajus
Copy link

gajus commented Mar 9, 2022

Feature Request

Is your feature request related to a problem? Please describe.

Current logs do not describe how long individual steps are taking.

Screen Shot 2022-03-09 at 5 35 50 PM

Describe the solution you'd like

It would be nice if the logs said how long each step took, e.g.

🔍 Searching the best cache archive available (25 seconds)
🌐 Downloading cache archive from bucket (40 seconds)
🗜️ Extracting cache archive (20 seconds)

Teachability, Documentation, Adoption, Migration Strategy

What is the motivation/use case for changing the behavior?

With this information I could seek for opportunities to optimize the process.

@jeremylvln
Copy link
Member

Hi!

I don't think this is something I want to have on the first steps (the lookup one especially). However, I can see the point of having a direct feedback when compressing/decompressing/downloading/uploading the file. I failed to find an easy way of doing this so I didn't did it on the initial release.

I don't see any issue if you want to try to implement this and submit a pull request! To be honest I don't think I will have the time more or less soon.

@jeremylvln jeremylvln added priority:low ❄️ This is a low priority task. Handle it when there is nothing else to do type:feature 🚀 Good for newcomers labels Mar 15, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
priority:low ❄️ This is a low priority task. Handle it when there is nothing else to do type:feature 🚀 Good for newcomers
Development

No branches or pull requests

2 participants