[strongSwan] Is there any locking contention point using the load tester plugin (strongswan 5.0.4)?

Chinmaya Dwibedy ckdwibedy at yahoo.com
Tue Nov 19 15:33:07 CET 2013


Hi,

With --enable-lock-profiler option, run with (#ipsec start --nofork) 100 IPsec tunnels without data traffic. Please note that, I have configured initiators and iterations to 10 in load-tester section of strongswan.config. I have disabled the logging and used pre-shared key authentication mechanism. During daemon shutdown, it prints the below time waited in each lock to console.

IKE Initiator
0.881188s / 602 times in lock created at: dumping 0 stack frame addresses:
0.438030s / 183134 times in lock created at: dumping 0 stack frame addresses:
0.1822s / 2809 times in lock created at: dumping 0 stack frame addresses:
77.478051s / 3317 times in lock created at: dumping 0 stack frame addresses:
0.2289s / 3357 times in lock created at: dumping 0 stack frame addresses:
0.24162s / 577 times in lock created at: dumping 0 stack frame addresses:
0.794s / 1151 times in lock created at: dumping 0 stack frame addresses:
0.1070s / 1613 times in lock created at: dumping 0 stack frame addresses:

IKE Responder

.36458s / 300 times in lock created at: dumping 0 stack frame addresses:
1.264847s / 602 times in lock created at: dumping 0 stack frame addresses:
0.675817s / 186885 times in lock created at: dumping 0 stack frame addresses:
147.318956s / 3107 times in lock created at: dumping 0 stack frame addresses:
71.114454s / 4017 times in lock created at: dumping 0 stack frame addresses:
0.5702s / 4057 times in lock created at: dumping 0 stack frame addresses:
0.32072s / 639 times in lock created at: dumping 0 stack frame addresses:
0.781s / 1114 times in lock created at: dumping 0 stack frame addresses:
0.1114s / 1600 times in lock created at: dumping 0 stack frame addresses:

Twice the time for the lock to become available is 147.3 and 71.1 seconds at IKE Responder end which is quite high and also once it is 77.4 seconds at IKE Initiator end. Is there any locking contention point in code? Any idea what might be the cause behind this and its remedy.

Regards,
Chinmaya





More information about the Users mailing list