Expand my Community achievements bar.

Don’t miss the AEM Skill Exchange in SF on Nov 14—hear from industry leaders, learn best practices, and enhance your AEM strategy with practical tips.
SOLVED

Scalability

Avatar

Level 1

Hi does anyone know where I get information on maximum concurrent numbers of users this platform could support?

We're currently scoping a video-chat gaming system which could have up to 10'000 concurrent users and need to establish reliability and scalability figure but I can't find any ...

Thank you

Sean

1 Accepted Solution

Avatar

Correct answer by
Former Community Member

With respects to the room user limits, the protocol used to connect to the service is irrelevant.

Thanks,

Fang

View solution in original post

4 Replies

Avatar

Former Community Member

Hi Sean,

Our only limitation is the number of users in a room.  Rooms are metaphors where users virtually rendezvous to collaborate and can be used to logically group your users for your application.  The current limit is 5,000 users per room.  However, there aren't any limits on the number of rooms that you can have.  So, you can easily distribute your 10,000 concurrent users across multiple rooms.

Thanks,

Fang

Avatar

Level 1

Cheers Fang,

and would there be any limits on RTMP connections if (very unlikely) a large proportion of the people were behind UDP restricted networs and the AV data had to go via the LiveCycle servers directly, or would it just automatically sclae up for us?

Avatar

Correct answer by
Former Community Member

With respects to the room user limits, the protocol used to connect to the service is irrelevant.

Thanks,

Fang

The following has evaluated to null or missing: ==> liqladmin("SELECT id, value FROM metrics WHERE id = 'net_accepted_solutions' and user.id = '${acceptedAnswer.author.id}'").data.items [in template "analytics-container" at line 83, column 41] ---- Tip: It's the step after the last dot that caused this error, not those before it. ---- Tip: If the failing expression is known to be legally refer to something that's sometimes null or missing, either specify a default value like myOptionalVar!myDefault, or use <#if myOptionalVar??>when-present<#else>when-missing. (These only cover the last step of the expression; to cover the whole expression, use parenthesis: (myOptionalVar.foo)!myDefault, (myOptionalVar.foo)?? ---- ---- FTL stack trace ("~" means nesting-related): - Failed at: #assign answerAuthorNetSolutions = li... [in template "analytics-container" at line 83, column 5] ----