How exactly is the peak concurrent connections index counted?

Hi, I’m confused about how you define a ‘device’ on Sendbird. From what I’ve read here, it seems a browser profile is the smallest unit (Case 2). However, in another discussion here, it appears that different tabs in the same profile might be counted as separate devices.

Could you clarify which is considered the smallest ‘device’?

  • Case 1: If tabs are the smallest, does using Sendbird chat on different tabs of the same browser profile count as one or multiple peak concurrent connections? If it’s one, please move on to Case 2.
  • Case 2: If a browser profile is the smallest, how would it be counted if a user opens an incognito tab or uses other browsers besides Chrome?
  • Case 3: If Case 2 isn’t correct, should I assume that individual browsers like Chrome, Firefox, Opera, etc., are considered the smallest units?

Hello @Tra_Phuong_Nguyen,

Welcome to the Sendbird Community.

It looks like we have some room to improve our documentation on this topic. PCC is ultimately the largest number of active websocket connections at any given time. So when we look at this in a browser context, it’s hard to tell you what a “unit” could consist of because it really depends on how you’ve implemented the SDK. If your application generates a single websocket connection for the user, and the user opens 10 tabs, then they could have 10 active websocket connections. That being said, our JS SDK will automatically disconnect the tabs that are backgrounded after 30 seconds, and reconnect them once they come to the foreground.

Now, this scenario can become much more complex because depending on how your application works, you could generate multiple websocket connections in a single tab if you’re creating multiple instances of the SDK and calling connect. In some senarios, such as using workers, you could even share a single connection across multiple tabs.

So ultimately, describing the smallest “unit” is not a simple topic.

1 Like