[GH-ISSUE #2587] API slows down after an average of 200 peers #5541

Open
opened 2026-08-05 01:03:48 -04:00 by saavagebueno · 0 comments
Owner

Originally created by @ismail0234 on GitHub (Sep 12, 2024).
Original GitHub issue: https://github.com/netbirdio/netbird/issues/2587

Describe the problem

The api slows down after 200 peers connected to the system. After 500 peers, it slows down a lot. Each request takes more than 1-2 seconds.

In the test measurements I made, these are the response times returned from the api according to the number of peers connected to the system.

20 Peers: 200-300 ms
100 Peers 300-600 ms
200 Peers: 500-1000 ms
500 Peers: 1500-3000 ms

JWT Group sync and User group propagation feature are also disabled. I do not use these features. Right now, I'm kicking all unconnected peers off the network every hour to keep the api running fast, so my problems are completely fixed. As the number of peers in the network increases, api calls become very slow and some calls return 0 http response.

The api calls I use are as follows;

  1. “List all Peers”
  2. “List all Groups”

Since Netbird does not share any information on the client side to find the id of the user in api calls, I need to match the netbird ip. For this, it is necessary to go through all peers and match the correct ip.

To Reproduce

  1. Connect 500 peers to System.
  2. Return all peers with the api.

Expected behavior

  1. Faster retrieval of data from the API or the option to filter the data instead of all of it.
  2. Instead of fetching all peers, it may be possible to search for only one peer with a method like “getPeerByIp” or “getPeerById”. In this way, we can use this method to find the desired peer instead of finding the correct peer among all peers.

Are you using NetBird Cloud?

Self-Hosted

NetBird version

0.28.9

Originally created by @ismail0234 on GitHub (Sep 12, 2024). Original GitHub issue: https://github.com/netbirdio/netbird/issues/2587 **Describe the problem** The api slows down after 200 peers connected to the system. After 500 peers, it slows down a lot. Each request takes more than 1-2 seconds. In the test measurements I made, these are the response times returned from the api according to the number of peers connected to the system. 20 Peers: 200-300 ms 100 Peers 300-600 ms 200 Peers: 500-1000 ms 500 Peers: 1500-3000 ms JWT Group sync and User group propagation feature are also disabled. I do not use these features. Right now, I'm kicking all unconnected peers off the network every hour to keep the api running fast, so my problems are completely fixed. As the number of peers in the network increases, api calls become very slow and some calls return 0 http response. The api calls I use are as follows; 1. “List all Peers” 2. “List all Groups” Since Netbird does not share any information on the client side to find the id of the user in api calls, I need to match the netbird ip. For this, it is necessary to go through all peers and match the correct ip. **To Reproduce** 1. Connect 500 peers to System. 2. Return all peers with the api. **Expected behavior** 1. Faster retrieval of data from the API or the option to filter the data instead of all of it. 2. Instead of fetching all peers, it may be possible to search for only one peer with a method like “getPeerByIp” or “getPeerById”. In this way, we can use this method to find the desired peer instead of finding the correct peer among all peers. **Are you using NetBird Cloud?** Self-Hosted **NetBird version** 0.28.9
saavagebueno added the management-serviceperformance labels 2026-08-05 01:03:48 -04:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: DYNR/netbird#5541