EFForg / EFForg/action-center-platform

Profile memory of different requests

Open
#7 0 comments 0 reactions 0 assignees View on GitHub
performance
Dominant language
Ruby
Stars
538
Forks
73
PR merge metrics
No merged PRs in 30d

Description

It would be nice to run a memory profiler on various requests, to make sure there aren't any long-running blocking calls:

https://github.com/tmm1/perftools.rb

Contributor guide

No contributing guide indexed for this repository

Research direction

The issue names no files or representative requests. Start by locating the application's request entry points, then review the perftools.rb profiler linked in the issue and run it against several request types. Done means the selected requests have profiling results and any long-running blocking calls are identified.

Written by the indexing model from the issue text.

Assessment

Tech stack
ruby
Domain
backend, performance
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.