Maximum Number of servers on a repeater?

[cascadecomputers]

I'm setting up a repeater in mode II, and before I get to far into my project and deployment, I began wondering what the maximum number of servers running in invers connection mode would be before the repeater became unstable? 10? 100? 1000? Does each invers connection to the repeater require (and hold) a specific amount of bandwidth?

I'd also be interested in the maximum number of active connections with various viewers.

I've only tested two active servers/viewers to this point. That seems to work fine. But, if I go ahead with this project, the number of invers connections could easily hit 300+ with 6-10 active viewers to various servers.

Does anyone have any experience with using this many? Or any thoughts as to what might happen with this many?

Mike Fynboh
Cascade Computers

[supercoe]

AFAIK the linux repeater is hard coded to stop at 1000 connections and the Windows one much sooner (100?).
The limitations would be:
1) Bandwidth (for active connections)
2) Memory + CPU
3) Hard coded limitation or windows socket limitation.

Does each invers connection to the repeater require (and hold) a specific amount of bandwidth?
Only the active connections require a significant amount of bandwidth.

Let us know how it works out for you.

[cascadecomputers]

Thanks Good enough for me to put the effort in. I'll try the Windows repeater first and see what happens (because I have a server available for that). If I know Linux will go up to 1000, then I can switch if it becomes an issue.

Bandwidth to the repeater isn't an issue and the servers and viewers will be in various locations. In the long run, if this works out and is stable, Memory and CPU won't be an issue. It will be worth the small hardware costs.

I'll let you know how it works out. I'm pretty hot on this project, so I should have the initial repeater and a dozen servers up by the end of the week.

Mike

[supercoe]

That would be great as I know the questions you are about to answer have been asked a lot around here.
Feel free to share any info you come across if you want to give back to the community!

[cascadecomputers]

Well, not going as fast as I'd like. I hit a problem when I reboot systems. Basically I can't connect, I just get the status window forever. If I restart the uvnc_service on the remote system, it works again. So, something is happening on reboot. I figure it has to have something to do with the service_commandline= in the ini file. But the heck if I know what. Going to let it rest for a few days ...

[cascadecomputers]

OK. I worked around the connection issue on reboot. It appears to be Win 7 systems that have the problem (and possibly Vista and Server 8, although I haven't confirmed that.) I resolved it by setting the uvnc_service to delayed auto start. It would appear that the uvnc_service is starting before something else that is required. I am betting that it is DNS. I could have probably got around it by hard coding an IP address into the service_commandline ... but that would limit me in the future. So, I added "sc config uvnc_service start= delayed-auto" to my batch file for installing and all seems well.

So, I've got install packages built and I'm going to start a larger deploy. Crossing my fingers ...

Mike