kilianc/rtail

Memory issues

Open

#118 opened on Jul 6, 2016

View on GitHub
 (6 comments) (0 reactions) (0 assignees)CSS (1,624 stars) (111 forks)batch import
bughelp wantedserver

Description

I have a server running these:

┌────────────────────────────┬────┬──────┬───────┬────────┬─────────┬────────┬──────────────┬──────────┐
│ App name                   │ id │ mode │ pid   │ status │ restart │ uptime │ memory       │ watching │
├────────────────────────────┼────┼──────┼───────┼────────┼─────────┼────────┼──────────────┼──────────┤
│ cha-api                    │ 0  │ fork │ 8477  │ online │ 21      │ 33D    │ 204.242 MB   │ disabled │
│ cha-website                │ 1  │ fork │ 3716  │ online │ 21      │ 29D    │ 187.551 MB   │ disabled │
│ cha-front                  │ 2  │ fork │ 8770  │ online │ 15      │ 33D    │ 138.719 MB   │ disabled │
│ rtail-server               │ 3  │ fork │ 30432 │ online │ 3       │ 55D    │ 508.676 MB   │ disabled │
│ rtail.cli-api              │ 4  │ fork │ 30474 │ online │ 2       │ 55D    │ 28.000 KB    │ disabled │
│ rtail.cli-website          │ 5  │ fork │ 30488 │ online │ 1       │ 55D    │ 28.000 KB    │ disabled │
│ rtail.cli-front            │ 6  │ fork │ 30502 │ online │ 1       │ 55D    │ 32.000 KB    │ disabled │
│ rtail.cli-ngx.access       │ 7  │ fork │ 30516 │ online │ 1       │ 55D    │ 32.000 KB    │ disabled │
│ rtail.cli-ngx.error        │ 8  │ fork │ 30530 │ online │ 1       │ 55D    │ 32.000 KB    │ disabled │
│ rtail.cli-ngx.front.access │ 9  │ fork │ 30544 │ online │ 1       │ 55D    │ 32.000 KB    │ disabled │
│ rtail.cli-ngx.front.error  │ 10 │ fork │ 30558 │ online │ 1       │ 55D    │ 32.000 KB    │ disabled │
└────────────────────────────┴────┴──────┴───────┴────────┴─────────┴────────┴──────────────┴──────────┘

Should rtail-server be using 500MB+ of memory? It's a server handling less than 100 requests per day.

Contributor guide

Tech stack
nodejs
Domain
backend
Issue type
performance
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.
1-3 hours
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.
mostly clear
Prerequisites
Node.jsBasic memory profiling
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
25
Research direction
Investigate the high memory usage of rtail server. Examine the server side code for potential memory leaks, especially in stream handling. Look at the Node.js process memory profiling to identify objects consuming memory. The issue body shows memory usage of over 500MB for a low traffic server. Check if there are any unreleased resources or accumulation of data.