Fork me on GitHub
#datomic
<
2021-09-14
>
steveb8n05:09:07

Q: I remember someone mentioning that using large/nested pull expressions in queries is slow. is that documented or explained somewhere? what’s the best alternative?

steveb8n05:09:30

I can think of these alternatives:

steveb8n05:09:06

1. query to get ids, map over each using d/pull

steveb8n05:09:15

2. return maps

steveb8n05:09:46

both assume in-mem access i.e. peer or Ion execution env

favila05:09:59

If you can consume and release results lazily, you can use qseq to delay realization of the pull.

steveb8n05:09:29

ah ok. so it’s not direct perf but instead about memory consumption. I presume this means a transducer can improve perf and mem when processing the results too