Known limits of SFS?

[Pippoflash]

Hi!
I am planning a complex application with SFS.
One of the architectural choices is to end up with thousands of persistent rooms.
Another option, more complex, is to create and destroy rooms on user login/logout.

Did someone ever test SFS with lots and lots of rooms allocated?
Is it very intensive for the server processor and memory wise?

thanks a lot
Pippo

[rsnail]

Hello,

So far we have had 600 rooms on one smartfox server with users in every room.

This used very little CPU ( 4-6% ) and 16% of the memory. Please note we are using a very fast dedicated server and we created our own custom extensions.

[Lapo]

Hi PippoFlash,

Did someone ever test SFS with lots and lots of rooms allocated?
Is it very intensive for the server processor and memory wise?

Sure, in one of our stress test we had this scenario:

- 1500 simulated users where connected to SFS
- Each one had a maximum of 20 requests to send to the server before being disconnected
- When user was disconnected a new one was created and logged in
- Each client request created a new room in the same zone
- The test was conducted for many days, with an average of 18-20.000 rooms running simultaneously in the zone.
- The test consumed very little cpu and about 160Mb of RAM

Another option, more complex, is to create and destroy rooms on user login/logout

This, in part, already exist.
If a user creates a room, his room will be destroyed when he goes away (when the last user inside leaves that room).

Our soon-to-come version 1.4 will add a lot of new server side commands and features to control / create / destroy rooms.
You can check the beta2 at this page >> http://www.smartfoxserver.com/download/beta/

Let me know if you have any other questions