Master Continuous Profiling on Kubernetes with Pyroscope: A Step‑by‑Step Guide

Developers often need to locate performance bottlenecks in production applications, but traditional log‑and‑code analysis can be time‑consuming and lack detail.

A modern approach is to apply continuous profiling techniques that highlight the slowest code paths consuming the most resources.

This article discusses continuous profiling and demonstrates using the open‑source tool Pyroscope to monitor microservices running on Kubernetes.

What Is Pyroscope?

Profiling analyzes a program’s memory, time complexity, or function call frequency and duration, helping developers optimize performance. Pyroscope is an open‑source platform that collects, stores, and queries profiling data efficiently, reducing CPU and memory consumption and improving user experience.

Profiling is a program analysis that measures memory usage, execution time, or function call frequency and duration, providing information for optimization.

Continuous Profiling

Continuous profilers enable faster, easier troubleshooting by continuously collecting code‑level performance data across the environment, quickly revealing resource‑intensive features after new code is introduced.

Which Continuous Profilers Exist?

Some popular continuous profiling tools include:

Pyroscope

Parca

Datadog Continuous Profiler

Google Cloud Profiler

Why Use Pyroscope?

Compared with other tools, Pyroscope focuses on a storage engine optimized for profiling data, supporting language‑specific agents for Go, Python, Ruby, eBPF, Java, .NET, PHP, and Rust, as well as eBPF‑based profiling.

Pyroscope uses a proxy‑server model to send profiles from applications to a central server, allowing efficient storage and query.

Parca relies on eBPF for sampling compiled languages, while Datadog and Google Cloud Profiler provide low‑overhead continuous profiling in production environments.

How to Install Pyroscope

“No matter whether you use Docker, Linux, or are looking for Ruby or Go documentation, Pyroscope can start a server and then an agent. Its custom storage engine enables fast queries even for long‑term profiling data.” – Pyroscope website

Use Minikube to create a Kubernetes cluster and install Pyroscope via Helm:

minikube start

helm repo add pyroscope-io https://pyroscope-io.github.io/helm-chart

helm install pyroscope pyroscope-io/pyroscope --set service.type=NodePort

helm list

kubectl get all

Integrating Pyroscope with the Google Microservices Demo

The demo modifies container images to include the Pyroscope binary, which starts the application and injects profiling.

Python Service

COPY --from=pyroscope/pyroscope:latest /usr/bin/pyroscope /usr/bin/pyroscope
CMD ["pyroscope","exec","python","email_server.py"]

.NET Service

COPY --from=pyroscope/pyroscope:latest /usr/bin/pyroscope /usr/bin/pyroscope
ENTRYPOINT ["pyroscope","exec","-spy-name","dotnetspy","/app/cartservice"]

Go Service

import (
    "github.com/pyroscope-io/pyroscope/pkg/agent/profiler"
)

func main() {
    pyroscope.Start(pyroscope.Config{
        ApplicationName: os.Getenv("APPLICATION_NAME"),
        ServerAddress:   os.Getenv("SERVER_ADDRESS"),
    })
    // code here
}

Update Kubernetes manifests to use the new images and add the SYS_PTRACE capability and environment variables for Pyroscope:

containers:
  - name: server
    env:
      - name: PYROSCOPE_SERVER_ADDRESS
        value: "http://pyroscope:4040"
      - name: PYROSCOPE_APPLICATION_NAME
        value: "email.service"
    securityContext:
      capabilities:
        add:
        - SYS_PTRACE

Deploy the manifests:

kubectl apply -f https://raw.githubusercontent.com/infracloudio/microservices-demo-dev/master/release/kubernetes-manifests.yaml

Expose the Pyroscope service: minikube service pyroscope Access the UI at the provided URL (e.g., http://192.168.49.2:30639).

Pyroscope’s CPU usage is low, and it stores data locally using the Badger database.

Resource Utilization

Monitoring Kubernetes pod resource usage and cost is important; Pyroscope adds minimal overhead.

Using Pyroscope for Monitoring

Pyroscope provides language‑specific agents and generates flame graphs for visual analysis.

Conclusion

Continuous profiling is essential for meeting end‑user expectations; detecting performance issues early prevents degradation of user experience. Tools like Pyroscope provide visibility into production code performance, helping reduce cloud infrastructure costs while delivering fast applications.