docs/getting-started/overview.md in polyphony-0.42 vs docs/getting-started/overview.md in polyphony-0.43

- old
+ new

@@ -414,31 +414,10 @@ The Polyphony HTTP server has a unique design that calls the application's request handler after all request headers have been received. This allows the application to better deal with slow client attacks, big file uploads, and also to minimize costly memory allocation and GC'ing. -Preliminary benchmarks show the Polyphony web server to be about 3X as fast as -Puma and 20X as fast as Unicorn. With SSL termination and using HTTP 2, the -Polyphony web server is about 2X as fast as Falcon. - -### HTTP/1 - -|Server|requests/sec|average latency|max latency| -|------|-----------:|--------------:|----------:| -|Puma| -|Unicorn| -|Agoo| -|Polyphony| - -### HTTP/2 with SSL Termination - -|Server|requests/sec|average latency|max latency| -|------|-----------:|--------------:|----------:| -|Falcon| -|Polyphony| - -(*Non-official benchmark with a basic "Hello world" Rack application. The usual -caveats regarding benchmarks should be applied here.*) +Benchmarks will be included here at a later time. ## Integrating Polyphony with other Gems Polyphony aims to be a comprehensive concurrency solution for Ruby, and to enable developers to use a maximum of core and stdlib APIs transparently in a \ No newline at end of file