This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-02-04
Channels
- # announcements (7)
- # beginners (37)
- # boot (6)
- # calva (13)
- # cider (13)
- # cljdoc (52)
- # cljs-dev (9)
- # clojure (117)
- # clojure-europe (3)
- # clojure-italy (12)
- # clojure-nl (21)
- # clojure-russia (8)
- # clojure-spec (77)
- # clojure-uk (20)
- # clojurescript (142)
- # community-development (6)
- # cursive (5)
- # datomic (13)
- # emacs (9)
- # figwheel-main (20)
- # fulcro (33)
- # graphql (11)
- # instaparse (6)
- # klipse (1)
- # off-topic (7)
- # om (8)
- # quil (7)
- # re-frame (11)
- # reagent (39)
- # reitit (10)
- # shadow-cljs (36)
- # spacemacs (3)
- # test-check (3)
- # tools-deps (83)
- # utah-clojurians (31)
- # vim (14)
what's the Y axis on this page? https://metosin.github.io/reitit/performance.html
yes, it’s the average nanos. the test matches all routes in the opensensors rest api suite and takes the average time for a match. It’s now 289ns for reitit-ring on my mac-book, while for compojure it’s 11615ns. Tried to make the routing trees as idiomatic per library for I could, hopefully done right. here are the tests https://github.com/metosin/reitit/blob/9af35647a87472cda67afc7cbca8127449e83e06/perf-test/clj/reitit/opensensors_perf_test.clj
i just benched a bunch of routes and in my app create-resource-handler is definitely the bottleneck