Im having trouble with concurrent HttpWebRequests/Responses scaling in our Mono 2.10.2 environment (Apache2). These are server-side requests made out to a REST API.
We are mimicking concurrent users by running these requests on separate threads and as the number of threads increases, the response time(s) increase as well. (i.e, 1 user = 300ms, 5 users=1500ms, etc) The exact same application in my local dev environment (.NET/Win7) scales as expected with no problems. We have increased ServicePoint.ConnectionLimit and have the following Apache configuration settings set in httpd.conf: MonoMaxActiveRequests (appname) 0 MonoMaxWaitingRequests (appname) 0 and in our mono application's configuration file: MonoSetEnv MONO_THREADS_PER_CPU=2000 Looking at a traffic monitor, it looks as though all HttpWebRequests are opened sequentially - as expected - but then only 1 or 2 ports/connections handle the responses. This would obviously cause a significant bottleneck. It is not network related as a similar PHP application works/scales as expected. Any thoughts? Thanks much. -- View this message in context: http://mono.1490590.n4.nabble.com/HttpWebResponse-concurrency-problems-tp4529621p4529621.html Sent from the Mono - General mailing list archive at Nabble.com. _______________________________________________ Mono-list maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-list
