igorkasyanchuk/rails_performance

Feature Request - Handle logging on another thread

Open

#67 opened on Dec 1, 2023

View on GitHub
 (1 comment) (0 reactions) (0 assignees)Ruby (91 forks)github user discovery
help wanted

Repository metrics

Stars
 (1,237 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

Would it make sense to wrap the rails_performance notification subscriber code branch with a Thread or Concurrent::Future so it can handle the payload prepearing redis writing on another thread?

Do you have any statistics on how much overhead of this gem on production, as in milliseconds or memory usage?

Contributor guide

Research direction
Investigate the current notification subscriber code and assess the possibility of using a separate thread to handle Redis writing. Also, gather statistics on gem overhead in production.
Tech stack
rubyrails
Domain
backendperformance
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.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
GitRubyRails
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40