This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # admin-announcements (25)
- # beginners (21)
- # boot (487)
- # cider (8)
- # clara (2)
- # cljsrn (35)
- # clojure (44)
- # clojure-austin (6)
- # clojure-russia (211)
- # clojure-uk (25)
- # clojurescript (225)
- # core-matrix (1)
- # data-science (3)
- # datomic (23)
- # events (1)
- # hoplon (9)
- # immutant (14)
- # jobs (1)
- # jobs-discuss (5)
- # ldnclj (3)
- # lein-figwheel (2)
- # off-topic (2)
- # om (65)
- # onyx (65)
- # parinfer (3)
- # pedestal (4)
- # proton (1)
- # protorepl (1)
- # re-frame (16)
- # reagent (3)
- # ring-swagger (1)
- # specter (11)
- # untangled (1)
- # yada (8)
lucasbradstreet: another PR for you: https://github.com/onyx-platform/onyx-datomic/pull/16
The versioned branch 0.8.x releases are really supposed to be just for cutting releases. GitHub makes it really hard to make this the default viewing branch, but then PR off master
is this the case in general for all onyx repos? should i generally branch off master?
so create a new branch off master in my fork, apply changes there, then PR back to onyx master?
Yup, I would probably just branch off master in your fork, cherry-pick the couple of commits from your PR branch, then PR back to master
Just as an initial comment, it looks good. I'm going going to drop the mapvs/and into  and just use regular maps with doalls, since it's more performant if you're not using it as a vector. It's probably a drop in the bucket but it's our default approach
go for it, could also just use a map instead of a mapv, and that would be the same thing
"In my opinion, the presence of doall, dorun, or even “unchunk” is almost always a sign that something never should have been a lazy sequence in the first place."
Please do. I was going to add a task bundle / new style test for it but if you want to handle it that'd be great
"We were in, however, need" the formulations feels a bit weird, no ? Shouldn't it be something like "We, however, were in need" ?
For those here dealing with Kafka and not in the onyx gitter channel, if you want to try a new kafka client and be a guinea pig for the alpha version, I've written a 0.9+ set of libraries for Kafka consumer, producer, admin, embedded server, serializers, partitioners, callbacks, etc. and growing. It needs some hands-on testing before an official version is posted, but it's working in my projects and codebases, no issues. If you have any feedback, problems, etc., I'd be happy to chat with you. Hope to make an Onyx plug-in using it when it is better tested. https://github.com/ymilky/franzy
Hey I’m trying to understand how messaging works. reading https://onyx.readthedocs.org/en/latest/user-guide/messaging/
I’m wondering how the connection scaling (m-squared vs n-squared) works? I thought Aeron used UDP in prod, so I was expecting that to be connectionless
Oh whoops, I need to delete our readthedocs account. We moved official docs to the website: http://www.onyxplatform.org/docs/user-guide/latest/messaging.html
Hi @lvh, Aeron is essentially building connections analogous to TCP on top of UDP, with the Aeron media driver being sort of like a userland TCP stack. The guarantees and performance will differ, but you get the point. The idea is that we only create one Aeron connection between two Onyx nodes, which is shared between v-peers, even though there exists m v-peers on the node.
@lvh If you're interested in Aeron in general, I'd recommend their Gitter. The devs who build it are really amazing folks.
It now shows the number of peers on each hosts, and it’ll show you which peers are allocated to jobs
I've not hugged Martin Thompson yet. He's on my list though. I only really met him at a job interview (I was the candidate) and then very quickly at a conference.
@greywolve: back to your post about doall. He's totally right that it's usually an antipattern. We've found that map + doall is faster than mapv so it's mostly what we do
If you don't return the transact results in write batch we'd use run! instead
It's nice to have the results in the event map for availability via lifecycles tho
I think it's really mostly a problem when you have the doall far away from the map
Anyway, this will be totally dominated by the transact so it's mostly academic