On Friday, March 2, 2018 at 12:48:28 AM UTC-5, Daniel wrote:
> How do you know this code is causing the error? Unless this is all your
> code does, descriptions of the error suggest the memory leak might be
> coming from anywhere. This tight loop might trigger too many successive GCs
> though: have you observed if the error only occurs under load, or under
> large time intervals? Some combination?
Okay, thanks for looking it over. This is a single-threaded, short lived
script, so this is the only thing happening. But it's possible there is an
unexpected large result set. I'll look into that. It may be smarter to use
`limit N` in my SQL, rather than the time range.
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to email@example.com
Note that posts from new members are moderated - please be patient with your
To unsubscribe from this group, send email to
For more options, visit this group at
You received this message because you are subscribed to the Google Groups
To unsubscribe from this group and stop receiving emails from it, send an email
For more options, visit https://groups.google.com/d/optout.