Do be honest, it probably doesn't do all that well. Making the container multi-process (as Moshe notes) would be a good first step to getting something worth benchmarking.
But, I should note, the obsession with benchmarks in WSGI containers is a symptom of a generally industry-wide lack of understanding of good performance analysis. The fastest WSGI container is probably 2% of your application's overhead; the slowest possible one, maybe 3%. The differences look huge when you're comparing servers against each other, but throw a real application and a database and some load balancer latency in there and the app server container utterly disappears. Even multi-process support isn't really about optimizing for performance (although certainly leveraging multiple cores helps), it's about being able to safely crash a WSGI container process without bringing down the whole server.
-glyph