Fork me on GitHub
#datomic
<
2015-07-21
>
robert-stuttaford05:07:15

ghadi: just be aware that ‘queries’ against the log don’t cache like index queries do

jballanc15:07:38

What would be the best way to log a request for the Datomic AWS support scripts?

arohner19:07:58

trying to debug a slow query, is there a way to find out how many segments were pulled down to do a query?

stuartsierra19:07:20

@arohner: Run it on its own, you can look at the :StorageGetMsec and :StorageGetBytes metrics in the Peer.

stuartsierra19:07:10

The :count is the number of requests to Storage.

arohner19:07:30

@stuartsierra: my local DB isn’t sending to cloudwatch, is there another way to get metrics?

stuartsierra19:07:58

@arohner: Yes, they are logged under the datomic.process-monitor Logger via SLF4J.

stuartsierra19:07:16

You can also attach your own metrics callback function.

arohner19:07:04

how? ctrl+f for ‘metrics’ and ‘callback’ are failing me in the API docs

jballanc20:07:53

@stuartsierra: would you be the person to handle a (very) simple request re: the AWS startup.sh script?

stuartsierra20:07:16

@jballanc: No, I don't know anything about that. I recommend the Datomic mailing list.

jballanc20:07:34

cool, thanks!

arohner21:07:32

are there any docs on how attrs of type :bytes are indexed?

arohner21:07:13

I’m using seek-datoms on :bytes, and it appears the iteration starts well before the value I pass in

arohner21:07:11

i.e. it appears the iteration starts at the first value in the attribute index, rather than right before value

arohner21:07:53

@stuartsierra: yeah, that looks suspicious. I have a gist testcase incoming