Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

💡 Feature request: Show performance stats

Open
#574 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 3 days

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
docker, rust

Research direction

Start by reading the request and identifying Redlib’s request handling and data-fetching entry points, then trace the stages from receiving a request through returning the rendered response. The issue asks for average timings across several time windows but leaves the measurements and performance view design open; done means users can inspect useful breakdowns to help identify slowdowns.

Written by the indexing model from the issue text.

Description

enhancement

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

Redlibs runs in Docker on my NAS. The typical response times range from 400 to 1500 (!) ms. I could be the weak CPU, it could be a bottle-necked connection, maybe a cache is too small or there's not enough free memory. I don't know why it's so slow because there's nothing that tells me the reason.

Describe the feature you would like to be implemented

To identify bottlenecks I would like to have some sort of performance view that breaks down what Redlib does and how long that took on average during the last 5m/15m/1h/1d. It could list Something like decoding request, contacting Reddit servers, downloading data from Reddit, format view from received data, provide user with processed data, etc. What-ever makes sense in regarding software architecture and helps debugging slowdowns. You know better than me what would be useful to show..

Additional context / screenshot

Ping times in the Firefox Extension LibRedirect (https://libredirect.manerakai.com/)

Image

Redlib boasts that it is one of the or the fastest Reddit frontends. But honestly, 400+ ms response times are kinda slow.

Dominant language
Rust
Stars
3.9k
Forks
293
Avg merge
14d 8h
Merged PRs (30d)
2

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

  • Ships a Dockerfile or Docker Compose file
  • No pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from redlib-org/redlib

All issues in redlib-org/redlib

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.