Learn how to use Winston’s built-in timer to benchmark code execution and calculate the overhead from making a request to an API.
- [Instructor] Let's start benchmarking code execution…within our application using the logger Winston.…When viewing a game,…there's a request to get the game in question…by ID from the game's API.…However, we have no idea how long that takes.…If you did the challenge video,…you added the request logger that uses…more into the game's API.…That will report how long it took…for the response to be built and sent.…What it doesn't tell us…is how long the entire transaction takes,…including the time that it takes to make the request…and send it across the network.…
With our application, everything is running locally,…so that's not really a factor.…But in a more distributed application,…that can be a very valuable piece of information.…Winston, the logger we're using for our application…includes a built in timer that can be retrieved…and started with a method, startTimer.…Then when execution is completed, execute timer.done…with a message to display the duration in milliseconds.…According to the documentation at the time of this writing,…
Author
Released
7/13/2018- Building a troubleshooting mindset
- Why measure performance?
- What's a microservice architecture?
- Managing microservices with PM2
- Effective logging strategies
- Debugging Node.js applications
- Benchmarking performance
- Profiling code execution
- Knowing what to optimize
Skill Level Intermediate
Duration
Views
Related Courses
-
Node.js: Testing and Code Quality
with Jon Peck3h 25m Intermediate -
Node.js: Design Patterns
with Alex Banks2h 11m Intermediate -
Node.js: Deploying Applications
with Kirsten Hunter1h 24m Intermediate
-
Introduction
-
What you should know3m 4s
-
Using challenges44s
-
Demo application tour4m 24s
-
1. Build a Troubleshooting Mindset
-
Finding what went wrong5m 11s
-
Why measure performance?3m 12s
-
Documenting problems2m 36s
-
When is a problem resolved?4m 10s
-
-
2. Introducing Microservices
-
3. Effective Logging Strategies
-
Why and what should I log?6m 26s
-
Choosing a logging library5m 40s
-
Request logging with Morgan6m 39s
-
Correlating requests in logs6m 18s
-
-
4. Debugging Node.js Applications
-
Debugging isn't just logging3m 51s
-
-
5. Measuring Performance
-
Benchmarking performance4m 51s
-
Profiling code execution7m 17s
-
-
Conclusion
-
Knowing what to optimize5m 13s
-
Caching fundamentals2m 54s
-
Next steps2m 23s
-
- Mark as unwatched
- Mark all as unwatched
Are you sure you want to mark all the videos in this course as unwatched?
This will not affect your course history, your reports, or your certificates of completion for this course.
CancelTake notes with your new membership!
Type in the entry box, then click Enter to save your note.
1:30Press on any video thumbnail to jump immediately to the timecode shown.
Notes are saved with you account but can also be exported as plain text, MS Word, PDF, Google Doc, or Evernote.
Share this video
Embed this video
Video: Benchmarking code with Winston