Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add pyroscope and memray #3435

Closed
HyeockJinKim opened this issue Jan 13, 2025 — with Lablup-Issue-Syncer · 0 comments · Fixed by #3459
Closed

Add pyroscope and memray #3435

HyeockJinKim opened this issue Jan 13, 2025 — with Lablup-Issue-Syncer · 0 comments · Fixed by #3459
Assignees

Comments

@HyeockJinKim
Copy link
Collaborator

HyeockJinKim commented Jan 13, 2025

Motivation  

[Why is this Story important? Explain the context and reasons for this feature or change.]  

  • Profiling of memory and CPU metrics is required when resource issues arise.

Required Features

[Clearly describe the features or functionality needed for this Story.]  

  • Add Pyroscope and Memray to the manager, agent, and storage proxy.
    • Enable them via configuration.
    • Add them to the common code and apply to each service.
  • Add a Pyroscope service in the Docker Compose setup.

Impact  

[Specify which components or services will be affected by this Story.]  

  • When checking resource usage, Pyroscope and Memray will make it easier to monitor CPU and memory metrics.

Testing Scenarios  

[Outline test cases or scenarios for validating the implementation.]

  • Check CPU profiles using Pyroscope.
  • Check memory usage using Memray.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant