A quick comment after we know where is the problem.(see previous mail) Being a newbie I wrote to this list in the first place. I couldn't really tell if it is or not wsgiref related.
Also sorry not to mention it sooner, at first i tried both the single-threaded/multithreaded scenarios and it made no difference. So I based the test cases using single-threaded server and single-threaded client only. I bumped into this problem using a library called Tilecache (tilecache.org), which provides little standalone script to try things out using simple_server.It's library to speed things up so the 3 seconds/request overhead was very bad. I think It would be nice to have a production quality HTTP-WSGI server in the standard library at least for low traffic sites. Tibor >> Just an idea, I have no idea about the workings of wsgiref, I've just seen >> this happening in other situations. > > It isn't really even wsgiref-related. First, wsgiref.simple_server is based > on the other stdlib HTTP server modules. > > Second, it's not intended for production use. > > Third, it's not multi-threaded, which is likely to be a factor if the > performance tests are done using concurrent requests. > > _______________________________________________ > Web-SIG mailing list > Web-SIG@python.org > Web SIG: http://www.python.org/sigs/web-sig > Unsubscribe: > http://mail.python.org/mailman/options/web-sig/tibor%40infinit.sk > _______________________________________________ Web-SIG mailing list Web-SIG@python.org Web SIG: http://www.python.org/sigs/web-sig Unsubscribe: http://mail.python.org/mailman/options/web-sig/archive%40mail-archive.com
