16 Apr
2015
16 Apr
'15
10:34 a.m.
I just tried the -t option in our sandbox, and it runs perfectly. I googled around but couldn't find the implications of this - increased overhead? Or just slightly increased response time due to requests queueing up instead of executing concurrently? Right now we only service 20 or so requests per minute, so I'm not too concerned about performance.
Then it'll be fine, just run with -t.
It limits the server to processing one request at a time. It may not handle large spikes in traffic well.
That may be an issue, we've had APs get kernel panics in the past, and saw 70-80 people re-authenticate in the space of 5 seconds. At any rate we now have a workaround, and as a bonus a great reason to finally push through an upgrade. Thanks guys!