If I need to have a pub/sub channel that has more subscribers than a
single twisted node can handle, is there a recommended approach to do
FWIW, we have tested (a single instance of) AutobahnPython with 180k concurrently active WebSocket connections running on 2 core VM with 4GB RAM. No issues.
broadcast across autobahn nodes? Not sure if this is something twisted
handles internally but I'm thinking along the lines of making the
subscriber list pull data from a db index.
AB (single Twisted process, single thread, single core) probably even scales to more than 200k connections, but a) I haven't tested and b) there obviously will be _some_ limit.
So you will need a scale-out architecture:
200k clients <----> AB1 <-------+
200k clients <----> AB2 <-------+
200k clients <----> AB3 <-------+-----> AB6
200k clients <----> AB4 <-------+
200k clients <----> AB5 <-------+
Here, AB1-5 acts as clients to AB6 ..
I'd be interested in your specific requirements (see my last mail) ..
Am 11.10.2013 00:37, schrieb Michael Salmon:
You received this message because you are subscribed to the Google
Groups "Autobahn" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to autobahnws+...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.