@lukaszkorecki that also works. Memory: What I saw on my machine is that memory goes up to 256mb but not higher. It could just be a GC thing? Like I said, if I put a GC at the end, memory seems to be consistent around 11mb. But just hooking it up to a cron job works.
@lukaszkorecki Wow, look at this:
./bb -Xmx128m -XX:+PrintGC -XX:+PrintGCTimeStamps -XX:+VerboseGC -e '(load-file "/Users/borkdude/Downloads/statsd.clj")' -e "(require '[statsd-client :as c]) (while true (c/increment :foo) (Thread/sleep 1))"
[Heap policy parameters:
YoungGenerationSize: 13421770
MaximumHeapSize: 134217728
MinimumHeapSize: 26843540
AlignedChunkSize: 1048576
LargeArrayThreshold: 131072]
It seems to respect all of those command line flags. When I use -Xmx64m
the memory usage seems to be consistent around 15mb.@lukaszkorecki Released as bb 0.0.85
@borkdude amazing! 🎉 I'll poke around the GC settings and see what's up :thumbsup:
@borkdude I set the heap size to 20m and so far, so good - it rarely goes over 12m usage (as measured by Docker) - I'm going to deploy this to our testing ECS cluster. Once it's battle tested in production, I'm going to open source this along with a detailed write up :-)