winstonjs/winston

[Feature Request]: Add benchmark tests

Open

#2096 opened on Mar 23, 2022

View on GitHub
 (0 comments) (0 reactions) (0 assignees)JavaScript (21,967 stars) (1,789 forks)batch import
Feature RequestGroomedHelp Wanted

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

Tech stack
javascriptnodejs
Domain
backendtestingperformance
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.
3-5 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Node.jsbasic performance testing conceptswinston usage
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50
Research direction
Review the pino benchmark implementation linked in the issue for structure and methodology. Identify key performance sensitive areas in winston (e.g., log creation, transports, formatting) by examining the source code. Propose a set of benchmark tests that measure these operations, ensuring they are repeatable and comparable.