This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2015-07-21
Channels
- # admin-announcements (24)
- # beginners (80)
- # cider (18)
- # cljs-dev (12)
- # clojure (94)
- # clojure-berlin (15)
- # clojure-dev (10)
- # clojure-gamedev (3)
- # clojure-italy (38)
- # clojure-japan (4)
- # clojure-russia (109)
- # clojure-sg (1)
- # clojurescript (161)
- # code-reviews (29)
- # core-async (17)
- # datomic (20)
- # editors (14)
- # instaparse (17)
- # ldnclj (9)
- # off-topic (9)
- # om (2)
- # onyx (2)
- # re-frame (11)
- # reagent (46)
ghadi: just be aware that ‘queries’ against the log don’t cache like index queries do
trying to debug a slow query, is there a way to find out how many segments were pulled down to do a query?
@arohner: Run it on its own, you can look at the :StorageGetMsec
and :StorageGetBytes
metrics in the Peer.
The :count
is the number of requests to Storage.
@stuartsierra: my local DB isn’t sending to cloudwatch, is there another way to get metrics?
@arohner: Yes, they are logged under the datomic.process-monitor
Logger via SLF4J.
You can also attach your own metrics callback function.
@stuartsierra: would you be the person to handle a (very) simple request re: the AWS startup.sh
script?
@jballanc: No, I don't know anything about that. I recommend the Datomic mailing list.
I’m using seek-datoms on :bytes, and it appears the iteration starts well before the value I pass in
i.e. it appears the iteration starts at the first value in the attribute index, rather than right before value
@arohner: Possibly related to https://groups.google.com/d/topic/datomic/zhDiEqNPb3A/discussion
@stuartsierra: yeah, that looks suspicious. I have a gist testcase incoming