|
|
On Tue, 2005-03-01 at 20:33 +0000, Jamie Lokier wrote: > I suspect he means the CPU load of the public-key crypto and > certificate checking at run time. With 10000 clients, that's a lot of > calculations. I'd expect he'd probably be okay with a beefy enough server once OpenVPN's multithreading support is back in place -- particularly if he boosts the key renegotiation interval, or (even better) has a client-connect script adding some random fuzz to the renegotiation interval (so as to stagger renegotiations even if all the clients initially connect at the same time). There still might be some trouble as everyone reconnects after downtime or a like event, but my guess is that it'd be workable. Be useful to know a bit more about what he's trying to do (and thus how critical it is for clients to reconnect promptly following downtime) to offer more suggestions -- but one could conceive of having the client instances configured to exit when disconnected from the server and running in a supervised scripting loop that places a random amount of delay before restarting the client instance; this would help to avoid the everyone-pile-on-the-server effect. James, what's the status of multithreading support? ____________________________________________ Openvpn-users mailing list Openvpn-users@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/openvpn-users Warning: require_once(../../../archive_common.php) [function.require-once]: failed to open stream: No such file or directory in /home/openvpn/domains/openvpn.net/public_html/archive/openvpn-users/2005-03/msg00043.html on line 202 Fatal error: require_once() [function.require]: Failed opening required '../../../archive_common.php' (include_path='/usr/local/lib/php') in /home/openvpn/domains/openvpn.net/public_html/archive/openvpn-users/2005-03/msg00043.html on line 202 |