|
|
At 09:15 PM 20/02/2006, Dale wrote: Hi, <thundering hurd description deleted> So it would seem that (and Iâ??m not a programmer) that the openvpn process/application needs to be multi-threaded to spawn off processes to utilize more processors? So along this line of thought, what about artificially splitting the client load by running two openvpn daemons and set each to a different UDP port bound to the same IP address and then split the remote network in half (via IP subnet) and assign each subnet half to one of the processes? I have plans to test this theory?maybe next weekend. Actually, why not just bind multiple instances to the same IP as you suggest and then have the clients load balanced on the various ports to spread the load. You dont have to change your toplogy nor have multiple client configs and it should be able to split the load this way among your different CPUs. At least, it would be interesting to see if it works in practice :) ---Mike ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! Openvpn-users mailing list Openvpn-users@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/openvpn-users |