Hi Steven. Ok, let´me explain our project: - We have a flash Card Game based on Red5. - There is one main Lobby (mainScope-ApplicationAdapter) that holds all our clients (initially). If one user goes to a game room (childScope) we create this scope dynamically.
Scenario: - When a client connects on our game, he goes directly to the main lobby and estabilish a connection to 2 so´s, one of them is responsable to show all connected users into this lobby and to receive and send chat lobby msgs (using so.send). The another so holds all rooms information (who is entering into a room game, who is leaving a room game, room points and another information). - When a user choices to go to a game room, he disconnects from the lobby (main scope) and connects into the game room (childScope). After he connects to this game room he estabilish a connection to 1 so, that holds room information about the players (who is entering into this game room and leaving), send and receive cards using so.send methods and chat msgs as well. Nowadays we have an average of 300 connected uses, 50 connected to the mainLobby ( each of them connected to 2 so´s) and 250 connected to 62 childScopes ( each of them connected to 1 so). Our server hardware is a P4 3.2ht, 2Gb RAM, 100Mb band located on CA, our clients playing from Brazil. I hope you can understand our scenario. Best Regards, Luiz Filipe. -----Mensagem original----- De: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] nome de Steven Gong Enviada em: domingo, 22 de abril de 2007 18:35 Para: [email protected] Assunto: Re: [Red5] 300 connected users - Red5 keeps freezing on 0.6r3release and from trunk as well Luiz, In order to find the root cause of this issue, I think we'd better have a test case to reproduce it. Is it possible for you to provide a test scenario that could possibly reproduce this freezing? Maybe you can describe what you have done with SOs in your application and I will try to write a case. On 4/23/07, Luiz Filipe <[EMAIL PROTECTED]> wrote: Hey guys, how´re doing. I just let you know that Red5 keeps freezing after 24hours with 300 simultaneous connected users. We have tried several approaches, like disable ghost connections, increase server memory and cpu, and others, but neither solved this problem. As our project is a typical card game application, we´re using sharedObjects on client and server to hold connected users, game rooms, who is on these game rooms, game methods based on so.send and so one. We´re thinking to change all our SharedObjects engine approach to NetConnections call´s, because that freeze problem is related with SO´s and maybe because using so´s on a large card game project isn´t the best solution. Do you guys have another opinion about that ? Thanks a lot for any help. Best Regards, Luiz Filipe. _______________________________________________ Red5 mailing list [email protected] http://osflash.org/mailman/listinfo/red5_osflash.org -- I cannot tell why this heart languishes in silence. It is for small needs it never asks, or knows or remembers. -- Tagore Best Regards Steven Gong
_______________________________________________ Red5 mailing list [email protected] http://osflash.org/mailman/listinfo/red5_osflash.org
