For Cute Chat 3.0, a single server will support about 2000 current users.

 

For coming Cute Chat 4.0, a single server will support about 4000 current users.

 

>>with an anticipated 50k - 200k attendees

 

It's too much for Cute Chat. You may need to find a java based solution.

 

>>Does this app sotre all active chats in the DB?

 

Yes.

 

>>I'm assumingou need the same sql server per chat room. 

 

That's not necessary. However you can split your users on multiple servers and SQL Servers.

 

To get good performance, it's better to set maximum users per room under 100. For example, if you have 5000 concurrent users, you can create about 50 rooms.

 

>>If you had multiple rooms you could split them up per sql servers? 

 

Yes, every room will have a URL. You can easily split the rooms into different sites:

 

For example:

 

 

 

 

 

 

>>I'm assumingou need the same sql server per chat room. 

 

> That's not necessary. However you can split your users on multiple servers and SQL Servers

 

Can you elaborate on this?  Are you saying I can have the same chat room (LocationID=4) with two web servers and each web servers connection string set to a seperate sql server and then users in that chat room would see each others chats regardless of what web server they were connected to?

 

Like, I'm connected via load balancing to web1 / sql 1 and you're connected to web2 / sql2 I would see your messages in the chat room and you would see mine?