[ANNs] growmonster and datomic-booties

growmonster helps you write database fixtures https://github.com/flyingmachine/growmonster datomic-booties helps you stand up a datomic database in boot (create the db, migrate schema and seed data, delete and recreate the db) https://github.com/fly

Re: which GC optimizations work better with Clojure?

I should mention here that if you are tuning the GC anywhere except at the end of your development cycle you're probably doing it wrong. 99% of the time you'll get better performance by reviewing your algorithms, running a CPU profiler, generating less garbage (via transients or something like that

Re: which GC optimizations work better with Clojure?

I've found Censum by jClarity to be an excellent tool to tune JVM GC parameters to your specific application running on a particular server. You add a few GC parameters to enable logging that the tool needs, run your app under load for enough time to get sufficient data, and then feed the log direc

Re: is reduce/reduced faster than loop/recur?

And just to add a pointer in case anybody's interested in opting in to this behaviour in a custom type, it's possible to do so by implementing clojure.core.protocols/IKVReduce (data.avl does this) or clojure.lang.IKVReduce (the iface implemented by built-in maps; clojure.core provides implementatio

Re: [ANN] components.md

I've quite enjoyed reading the various approaches to using Component (or not as the case may be), so much so that I've added my own two pence: http://derek.troywest.com/articles/how-i-use-component On Tuesday, April 5, 2016 at 6:28:48 PM UTC+10, Renzo Borgatti wrote: > > Hello clj, > > kinda la

Re: Schemas for DSLs on top of Clojure

Ok. Thank you. Not quite what I was expecting but nice to see that tool too. On Friday, 29 April 2016 20:45:27 UTC+2, Michael Willis wrote: > > The convention that I've seen among the Clojure community is to represent > these kinds of things as data structures, and define your contraints using

which GC optimizations work better with Clojure?

GC parameters used by a lot of projects are handed down like traditions for years, even spreading to others. They're almost never re-evaluated, which means they might actually lose out on new performance improvements, or worse, might even cause performance regressions. Most parameters in the Ov