openfoodfacts/openfoodfacts-server

Perl code profiling and mod_perl memory leaks tracking and debugging

Open

#1,796 opened on May 23, 2019

View on GitHub
 (2 comments) (1 reaction) (0 assignees)Perl (236 forks)batch import
Perlhelp wantedinfrastructure🎯 P0🚅 Performance

Repository metrics

Stars
 (477 stars)
PR merge metrics
 (Avg merge 15d 21h) (157 merged PRs in 30d)

Description

What

  • We have not done any profiling of the Perl code of the server, it is very likely that there are performance issues that we could solve, if we find them. Same for memory leaks: our mod_perl process grow very big very fast. There are a number of tools for Perl code profiling and memory usage tracking that we could try to find.
  • This bug is to list our experiments and what we find.

Part of

  • #8764

Contributor guide

Research direction
Research and document available Perl profiling tools (e.g., Devel::NYTProf, Devel::DProf) and memory leak detection tools for mod perl, then conduct experiments to identify performance bottlenecks and memory leaks in the server code.
Tech stack
None
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-2 days
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.
Clear
Prerequisites
Perl
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30