On Thu, Apr 23, 2015 at 1:34 AM Paul deGrandis paul.degran...@gmail.com
wrote:
I'd also encourage you to reconsider your benchmark - ask yourself, What
does this really tell me? Is the benchmark an accurate representation of
the kinds of HTTP services you build? Are the payloads (parsing
Hey,
I'm curious what you are trying to measure in regards to Clojure. As far as
I know there is not a single Web Server actually written in Clojure, they
are all written in Java and we just use them. The Compojure benchmark you
linked uses the default Jetty Adapter for Ring (like Rack in Ruby
On 23 April 2015 at 00:34, Paul deGrandis paul.degran...@gmail.com wrote:
Also note that Compojure (and Ring) applications are artificially
limiting, because they cannot utilize the containers' full capabilities
(Ring apps can't go async at the container level, they can't use NIO
responses,
Also note that Compojure (and Ring) applications are artificially limiting,
because they cannot utilize the containers' full capabilities (Ring apps
can't go async at the container level, they can't use NIO responses, etc).
For these use-cases, you'll have to program directly to container
You should check your sources. http-kit is not written in Clojure and does
not use netty.
On Wednesday, April 22, 2015 at 11:40:21 PM UTC+2, François Rey wrote:
On 22/04/15 20:22, Thomas Heller wrote:
As far as I know there is not a single Web Server actually written in
Clojure, they
On 22/04/15 20:22, Thomas Heller wrote:
As far as I know there is not a single Web Server
actually written in Clojure, they are all written in Java and we
just use them.
http-kit would be one,
although it's using netty which is a
On 23/04/15 00:49, Thomas Heller wrote:
You should check your sources. http-kit is not written in Clojure and
does not use netty.
You're right, I looked at it too quickly: the src directory is mostly
java and the project.clj has a dev only dependency to netty.
I always thought it was written in
Hi,
I'm trying to build up a different kind of web server framework benchmark,
where measurement is not on peak performance, but on capacity and latency.
That is, the numbers we keep stable are:
* 10k connections
* 30k req/s
* 2053 bytes of static content served by a GET request on a simple
