Skaperen
good enough. i will be running many processes of OpenVPN in a few cases. i am putting together a tunnel scheme where the users don't need to deal with tunnel addresses ... for AWS users, to setup region to region tunnels, which could be as many as 13 processes per instance (if someone is using all 14 regions). it's in an AMI. just launch it in each region of interest and that instance finds all the others in the same AWS account and sets up the tunnel. when i ran it in all 14 regions myself, as a test, on a one core instance, it was slowing down rather significantly (one core divided up among 13 processes).
this scheme picks a random port for each tunnel, and exchanges that between regions along with keys. that way many tunnel endpoints can end in the same one instance.
maybe i can run two processes, one tunnel for each direction (different ports). that could at least be a win on 2 core instances. other tricks could involve dividing up traffic over many tunnels to have many processes using many cores for the more common cases of just 2 or 3 regions.