This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-08-01
Channels
- # aleph (3)
- # announcements (10)
- # babashka (6)
- # bangalore-clj (4)
- # beginners (91)
- # biff (7)
- # cider (25)
- # cljs-dev (1)
- # clojure (109)
- # clojure-europe (9)
- # clojure-norway (5)
- # clojure-uk (1)
- # clojurescript (22)
- # cursive (22)
- # data-science (1)
- # datalevin (5)
- # datomic (7)
- # emacs (7)
- # etaoin (1)
- # events (3)
- # graphql (12)
- # hyperfiddle (1)
- # inf-clojure (1)
- # lsp (69)
- # luminus (1)
- # meander (21)
- # nbb (4)
- # off-topic (27)
- # other-languages (12)
- # rdf (58)
- # releases (3)
- # remote-jobs (2)
- # rum (12)
- # shadow-cljs (4)
- # sql (3)
- # xtdb (1)
Heya, does anyone know what exactly the advantage is of using netty-transport-native-epoll over Netty's default NIO based transport? Since JDK 9, the latter also uses epoll on Linux by default (cf. https://bugs.openjdk.org/browse/JDK-8142872) which makes me wonder :thinking_face:
Ha, found some anecdotal evidence in the issue tracker that it could be more performant: https://github.com/clj-commons/aleph/issues/475#issuecomment-460428052
last time i tested (which was like two years back) epoll performed much better. i can't find the records anymore but iirc nio had to run through much more stuff and the stack depth showed. (also you need to specify architecture too when you use the native transport packages, like [io.netty/netty-transport-native-epoll "4.1.50.Final" :classifier "linux-x86_64"] )