# Pulp Service Performance Brian's buckets - Application Performance - Resource Allocation - Throughput # Goals 1. Understanding and scaling throughput 2. Request latency # Questions * How can we right-size the CPU and RAM limits for the api, content, and worker processes? * How do we characterize typical workloads on the api, content, and worker processes? * Do we need process recycling, and if so when? * Do we have any memory leaks? * What are the traffic volumes that we expect for the various components? * Can we horizontally scale enough to reach these traffic levels? # Workload characterization * Analyze the API calls * Analyze the task record
Last changed by  
 
Pulp
Design/Discussion/Meeting minutes for https://pulpproject.org/
26

Read more

RPM meeting

discuss adopting zero-downtime-migration strategy

5/16/2024
Pulp/AH integration team meeting

Old link for the meeting notes https://hackmd.io/mrVY2804QnS1_xjQcx0p1gOld link for the pulp-container meeting notes* https://hackmd.io/z7i694VeTR-p4hgTk2Oocw

5/15/2024
Deployers Team Meeting

Triage Query:https://github.com/pulp/pulp-oci-images/issues?q=is%3Aissue+is%3Aopen+label%3ATriage-Neededhttps://github.com/pulp/pulp-operator/issues?q=is%3Aissue+is%3Aopen+label%3ATriage-Needed

5/14/2024
Pulpcore/katello/pulp_deb integration meeting

See also: https://discourse.pulpproject.org/t/katello-pulp-community-integration-meeting-minutes/39

5/14/2024
Read more from Pulp
Published on HackMD