winstonjs/winston

[Feature Request]: Add benchmark tests

Open

#2,096 opened on Mar 23, 2022

View on GitHubContributor guide
 (0 comments) (0 reactions) (0 assignees)JavaScript (1,789 forks)batch import
Feature RequestGroomedHelp Wanted

Repository metrics

Stars
 (21,967 stars)
PR merge metrics
 (Avg merge 68d 4h) (9 merged PRs in 30d)

Description

🔎 Search Terms

Performance, Benchmarks, Analysis

The vision

Add a suite of tests that can be used to make more informed decisions regarding the performance impact of proposed changes, as well as a means of determining the least optimized implementations in the current state of Winston

Use case

No response

Additional information

Example implementation: https://github.com/pinojs/pino/blob/master/benchmarks/

Contributor guide

Research direction
Study the pino benchmark example and Winston's existing test structure. Create a benchmark suite using a tool like 'benchmark' or 'mitata' to measure performance of logging methods. Compare different transport configurations and message sizes. Run benchmarks and document results.
Tech stack
javascriptnodejs
Domain
backend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
JavaScriptNode.js
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40