Fork me on GitHub
#reitit
<
2019-05-29
>
orestis07:05:38

You can actually get reitit to play nice with just evaluating your routes again. There is even something in the docs

👍 1
orestis07:05:48

And if you’re using pedestal, here’s my workaround: https://github.com/metosin/reitit/issues/261#issuecomment-496006361

ikitommi08:05:35

with component & integrant, the routes can depend on other components, e.g. more routes for dev-mode, generate routes from db. I have a hotkey for integrant reset (& save all files) in Cursive, the reset is subsecond, so quite ok.

👍 2
valerauko12:05:11

I'd be interested to see how much mileage you could get/lose if you swapped immutant for aleph

juhoteperi12:05:44

@vale Two of those results already include numbers for Aleph

juhoteperi12:05:19

These plaintext/JSON/single query tests don't really test routing, so they are mostly just benchmark of tuned Immutant server (and Jsonista)

ikitommi12:05:21

the perf is combination of all. plain-text with slow routing lib is many times slower than with a fast routing lib: the response generation is fast, so the routing dominates.

ikitommi12:05:23

but, current release of immutant is much slower, about 2x in my perf tests, using my own perf-fork in the tests.

ikitommi12:05:01

I would say both Aleph & Immutant(perf-fork) are really fast, the latter bit faster, but just tens of percents, which shoudn’t matter.