This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-03-03
Channels
- # admin-announcements (2)
- # beginners (18)
- # boot (118)
- # cider (12)
- # cljs-dev (12)
- # cljsrn (24)
- # clojure (142)
- # clojure-art (4)
- # clojure-bangladesh (3)
- # clojure-ireland (1)
- # clojure-italy (7)
- # clojure-norway (4)
- # clojure-poland (207)
- # clojure-russia (101)
- # clojurescript (108)
- # clojurewerkz (2)
- # core-async (6)
- # css (8)
- # data-science (23)
- # datomic (31)
- # devcards (2)
- # emacs (8)
- # funcool (25)
- # hoplon (34)
- # immutant (78)
- # ldnclj (7)
- # lein-figwheel (4)
- # leiningen (6)
- # luminus (35)
- # off-topic (1)
- # om (119)
- # onyx (43)
- # parinfer (29)
- # proton (11)
- # re-frame (25)
- # remote-jobs (1)
- # slack-help (1)
- # spacemacs (3)
- # yada (10)
@michaeldrogalis: beginners-guide is awesome :thumbsup:
@acron: Thanks! I guess I should actually finish it now that folks are unearthing it from nearly a year ago.
We now have a newrelic onyx-metrics plugin
It was painful to write. The java api kinda sucks and then I found out that it just does REST calls anyway, so I switched to the REST API
@michaeldrogalis: it depends on the job-metadata functionality, so it’ll only get shipped with 0.9.0
@lucasbradstreet: Okay, sounds good. Glad we got that patch ready.
Jepsen post is getting there
blown away by those posts you recommended my last night @lucasbradstreet, had no idea how relatively weak ec2 instances were
Yeah, I couldn’t figure out why my 6 core Xeon v2 was besting a 8 core v2 on EC2
I don’t think it makes EC2 necessarily a bad deal, it’s just annoying that it’s easy to be fooled by their specs
totally
For a while I was under the impression that they somehow just had absurdly low prices compared to buying hardware. Makes a lot more sense now.
Yeah, you're actually paying a lot for the flexibility they give
What's surprising is that there aren't any 36 core machines via dual socket 18 core CPUs
I had no idea there were even 18 core chips
last time I bought a cpu was during the core 2 quad days
I'm sure Intel will have 30+ core CPUs in a few years
How'd the bench look after those changes?
latency didnt drop much but throughput did
restarting kubernetes with 6 nodes
You can dynamically add more nodes, I’m just doing chores around the house and am too lazy to go through the setup process, rather just edit the numbers in the cloudformation scripts 😉
Is the only way to get an instance limit increase with AWS to use their support system?
as far as I know, yes
but usually they are OK with it and respond fairly quickly
cool thanks
like, under 2 days
(in the “I won’t pay a thing” support plan)
can also be done in just a few hours. Just, there is no commitment if you don’t have support.
@gardnervickers: we should bump those every time we get a chance
I'd like to have a really high limit there
I noticed that the sample-catalog from the template requires the fn it uses. Is that necessary? On the one hand, the catalog just refers to it as a keyword, but I could see how it needs to be required somewhere for that keyword to be resolvable to the actual fn. Or does that always work by default?
That’s not necessary
It only needs to be required by code that is running on the peers
I dont believe it’s included in the jar if you dont require it somewhere.
Typically we do this in the code that launches the peers https://github.com/onyx-platform/onyx-template/blob/0.8.x/src/leiningen/new/onyx_app/src/onyx_app/launcher/launch_prod_peers.clj but you could do it in a separate namespace (so you could require it in your tests and such too)