This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-07-19
Channels
- # admin-announcements (2)
- # aws-lambda (3)
- # beginners (66)
- # boot (61)
- # cider (1)
- # cljs-dev (17)
- # clojure (100)
- # clojure-austin (4)
- # clojure-brasil (1)
- # clojure-canada (8)
- # clojure-quebec (6)
- # clojure-russia (48)
- # clojure-sg (6)
- # clojure-spec (37)
- # clojure-uk (61)
- # clojure-ukraine (2)
- # clojurescript (80)
- # core-async (13)
- # cursive (20)
- # datascript (37)
- # datomic (2)
- # defnpodcast (4)
- # emacs (5)
- # funcool (3)
- # hoplon (11)
- # jobs (7)
- # juxt (26)
- # lein-figwheel (48)
- # leiningen (3)
- # luminus (3)
- # om (34)
- # om-next (5)
- # onyx (5)
- # protorepl (6)
- # re-frame (10)
- # reagent (9)
- # rethinkdb (16)
- # ring-swagger (5)
- # spacemacs (14)
- # specter (54)
- # untangled (36)
- # vim (75)
- # yada (1)
@klmn: Thanks, glad to know that someone else is using the same architecture and processing more data than us - it can get lonely being on the cutting edge! 😃
Are onyx’s windowing aggregation functions like :onyx.windowing.aggregation/sum
just for convince? Or do they offer some performance benfiet? I assume I can perform an arbitrary calculation on a window on a trigger. For example sum
or standard deviation
. If the benfiet is performance, because the sum is updated in real time, then could you role your own auto-updating function like standard deviation?
You'll need to create your own aggregation following the pattern in onyx.windowing.aggregation. It is there that you provide the logic for updating a window, and merging discrete window states.
You can perform arbitrary computation on the trigger, but you want to avoid using stuff like conj and then triggering on all the segments because it'll mean checkpointing the full segments, rather than the computation results / differences
Onyx 0.9.9 is out. Just a small bug fix this time around.