You usually wanna go with apache with mod_mono on a production deployment. mod_mono at least has a good behavior under load. It doesn't have problems with concurrent connections. Apachebench on httpd2-cvs, mod-mon-cvs gives me the following numbers on my 800MHz athlon box with 300MB RAM when running xsp/test/index.aspx with concurrency=200 (no caching). Like any other benchmark, your mileage may vary.
Concurrency Level: 100 Time taken for tests: 345.85596 seconds Complete requests: 2000 Failed requests: 0 Write errors: 0 Total transferred: 21026000 bytes HTML transferred: 20474000 bytes Requests per second: 5.80 [#/sec] (mean) Time per request: 17254.280 [ms] (mean) Time per request: 172.543 [ms] (mean, across all concurrent requests) Transfer rate: 59.50 [Kbytes/sec] received
Connection Times (ms)
min mean[+/-sd] median max
Connect: 0 2 12.3 0 82
Processing: 7673 16107 3658.2 15580 99947
Waiting: 7572 16056 3660.1 15533 99923
Total: 7706 16110 3657.3 15580 99947-fawad
Tiago Lima wrote:
Hi,
What is the best way to deploy a site (ASP.NET .aspx) using mono?
Do you use xsp only, apache with mod_mono?
Does the site has a correct behaviour when receiving multiple simultaneous requests?
For example, ~20+ simultaneous users...
Does anyone has any experience on this?
Thanks in advance,
Tiago Lima
_______________________________________________ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list
