I&#39;m experiencing some strange behaviour with my test app. I&#39;ve about 50 simultaneous GET requests that I send to the same server. The server is an embedded server on a small piece of hardware with very limited resources. In order to optimize the performance for each single request, I configure one instance of `Alamofire.Manager` as follows:

    let configuration = NSURLSessionConfiguration.defaultSessionConfiguration()
    configuration.HTTPMaximumConnectionsPerHost = 2
    configuration.timeoutIntervalForRequest = 30
    let manager = Alamofire.Manager(configuration: configuration)

When I send the requests with `manager.request(...)` they get dispatched in pairs of 2 (as expected, checked with Charles HTTP Proxy). The weird thing though is, that all requests which didn&#39;t finish within 30 seconds from the first request, get cancelled because of the timeout at the same time (even if they haven&#39;t been sent yet). Here is an illustration showcasing the behaviour:

![concurrent request illustration][1]

Is this an expected behaviour and how can I make sure that the requests won&#39;t get the timeout before they are even sent?

Thanks a lot!


  [1]: http://i.stack.imgur.com/gjXC8.png

All Nsurlsessionconfiguration Solutions on Gang of Coders

Total of 1 Nsurlsessionconfiguration Solutions

NSURLSession concurrent requests with Alamofire