Investigating performance issues

First step to investigate what's going on with your Centrifugo is looking at information provided by info command. There are 2 ways to get this information:

• send info command with HTTP API client
• send info command from actions tab of admin web interface

In general you should configure Centrifugo monitoring to periodically send Centrifugo metrics to external monitoring system.

But sometimes looking at metrics is not enough. In this case you can additionally capture CPU and heap profiles from running Centrifugo node.

To be able to do this Centrifugo must be run with debug configuration option enabled:

centrifugo --config=config.json --debug

Or with "debug": true in configuration file.

When debug enabled extra HTTP handlers become available on internal port.

Assuming your Centrifugo address is https://centrifugo.example.com then go to https://centrifugo.example.com/debug/pprof/ and you will find debug information.

If you modified internal address or port when starting Centrifugo you should use that custom address and port to access debug data.

To capture CPU profile:

curl https://centrifugo.example.com/debug/pprof/profile > /tmp/cpu.profile

To capture heap memory profile:

curl https://centrifugo.example.com/debug/pprof/heap > /tmp/heap.profile

Both profiles can provide some insights to what's going on and why Centrifugo consumes a lot of memory or lot of CPU time.

There many articles describing how to work with profiles in Go, some of them:

• Debugging performance issues in Go programs
• A Pattern for Optimizing Go

But you can just show you profiles to us in Gitter chat (please put profiles into ZIP archive before uploading).