Thanks Jim, that's terrific!
For those following, updated results now
available: https://github.com/ptaoussanis/clojure-web-server-benchmarks
--
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send e
tic!
>>>
>>> For those watching: Xfeep's fixed a number of config issues, updated all
>>> the servers, and completely updated the chart.
>>>
>>> Absolutely well worth a look if you're interested in Clojure web server
>>>
;> Absolutely well worth a look if you're interested in Clojure web server
>> performance.
>>
>> * Results are here:
>> https://github.com/ptaoussanis/clojure-web-server-benchmarks
>> * His GitHub page: https://github.com/xfeep
>> * His nginx/clojure lib: htt
> performance.
>
> * Results are here:
> https://github.com/ptaoussanis/clojure-web-server-benchmarks
> * His GitHub page: https://github.com/xfeep
> * His nginx/clojure lib: https://github.com/xfeep/nginx-clojure
>
> Cheers! :-)
>
> --
> *Peter Taoussanis*
&g
Oh wow, that's fantastic!
For those watching: Xfeep's fixed a number of config issues, updated all
the servers, and completely updated the chart.
Absolutely well worth a look if you're interested in Clojure web server
performance.
* Results are here:
https://github.com/ptaoussa
I have committed some update.
- org.clojure/clojure 1.4.0 --> 1.5.1
- compojure 1.1.4 --> 1.1.6
- ring 1.1.6 --> 1.2.1
- aleph 0.3.0-beta13 --> 0.3.0
- http-kit 1.3.0-alpha2 --> 2.1.16
- ring-netty-adapter 0.0.3 --> netty-ring-adapter 0.4.6
- remove testing about pure nginx w
>
> You are welcome.
> My Github user name is xfeep.
> I'm glad to join the repo. Thanks for your invitation!
>
Okay, great - I have added you. You can make any changes you like. I would
be happy if you or someone else wants to maintain (update) the repo.
Cheers :-)
--
*Peter Taoussanis*
--
-
You are welcome.
My Github user name is xfeep.
I'm glad to join the repo. Thanks for your invitation!
On Monday, January 13, 2014 2:42:44 PM UTC+8, Peter Taoussanis wrote:
>
> Hi Xfeep,
>
> Thank you, I could never understand what configuration (setting) was
> wrong. I do not have time to upd
max concurrent level is only 96).
>
>
>
> On Saturday, January 5, 2013 11:52:57 PM UTC+8, Peter Taoussanis wrote:
>>
>> Hi all,
>>
>> Quick post to mention that I've put up some rough benchmarks for a number
>> of Clojure web servers:
>> ht
Hi Xfeep,
Thank you, I could never understand what configuration (setting) was wrong.
I do not have time to update the project now, but if you give me your
GitHub user name - I can add you to the repo?
You can update the tests and/or results if you want to.
Thank you also for your work on nginx-
put up some rough benchmarks for a number
> of Clojure web servers:
> https://github.com/ptaoussanis/clojure-web-server-benchmarks.
>
> Getting semi-reliable numbers was a real PITA, and I'm sure there's still
> plenty of room left for improvement (suggestions welcome!). Usual
Hey, thanks for point out latency, I haven't look at them deeply. Here is
how http-kit compare to Nginx when concurrency is 96:
Server Software:http-kit
Server Hostname:127.0.0.1
Server Port:8087
Document Path: /
Document Length:1163 bytes
Concurr
On Jan 25, 4:24 pm, Peter Taoussanis wrote:
> Hi Dmitry,
>
> Raw bench results are provided in the `results`
> folder:https://github.com/ptaoussanis/clojure-web-server-benchmarks/blob/mas...
>
> There you'll find a breakdown of the times to connect, process, and wait.
>
On 2013-01-25, at 6:24 AM, Peter Taoussanis wrote:
> I'd consider adding a graph if folks think these numbers are sufficiently
> interesting?
>
That would be great! This is very important information for me. And, unless
things have improved markedly over that last year or so (I hope so), I t
Hi Dmitry,
Raw bench results are provided in the `results`
folder:
https://github.com/ptaoussanis/clojure-web-server-benchmarks/blob/master/results/20130116-01-25
There you'll find a breakdown of the times to connect, process, and wait.
Also the cumulative % of requests served relative t
It would be *really* nice to see latencies as well. Some webservers trade
latency to throughput, and there is no point in throughput if your service
is hardly usable due to 100ms+ responses.
On Wednesday, January 16, 2013 10:56:23 AM UTC+4, Peter Taoussanis wrote:
>
>
> This is very interesting.
> This is very interesting. Have you tried running the Ring Jetty adapter
> with a larger thread pool? It's set lower than the default so as not to
> overload cloud hosts like Heroku.
>
Okay, bumped the :max-threads from 50 to 100 without seeing much change to
the results at these relatively
>
> This is very interesting. Have you tried running the Ring Jetty adapter
> with a larger thread pool? It's set lower than the default so as not to
> overload cloud hosts like Heroku.
>
You mean the :max-threads? No, I left it at the default (50, if I recall
correctly?). I'll try bump it nex
#x27;ve put up some rough benchmarks for a number
> of Clojure web servers:
> https://github.com/ptaoussanis/clojure-web-server-benchmarks.
>
> Getting semi-reliable numbers was a real PITA, and I'm sure there's still
> plenty of room left for improvement (suggestions welco
A couple folks asked for higher concurrency numbers, so I've bumped the max
to 92. Many of the servers can comfortably hit 500+ on my hardware, but
others begin acting erratically.
Want to first eliminate the possibility that the trouble is on my end (e.g.
OS TCP tuning), then I'll bump the num
Hi all,
Quick post to mention that I've put up some rough benchmarks for a number
of Clojure web
servers: https://github.com/ptaoussanis/clojure-web-server-benchmarks.
Getting semi-reliable numbers was a real PITA, and I'm sure there's still
plenty of room left for improveme
21 matches
Mail list logo
