neil VS criterium

So neil has a bunch of other features like project scaffolding, building, testing, adding license, etc. I really recommend you take a deep look at the repository and learn all the automatized possibilities that neil adds to your project.

Check out neil. It makes creating new deps.edn-based projects easy. It also has commands to add deps incrementally to your deps.edn with neil dep add and helps you tag new releases with neil version. You can run it in a REPL if you want, but as you can see below, it runs pretty fast in the shell. $ brew install babashka/brew/neil $ time neil new scratch play Creating project from org.corfield.new/scratch in play neil new scratch play 0.09s user 0.06s system 54% cpu 0.280 total

Full-featured test runner: https://github.com/lambdaisland/kaocha

If you install neil (https://github.com/babashka/neil), you can do `neil add test` which will automatically set up cognitect-labs/test-runner in your project. Then you can run tests with `neil test` (just an alias, you don't have to use it).

> I used Kit to bootstrap this project and the way it set up tests doesn't even work, but this was what most people recommended to me for starting a Clojure project

I don't really like the approach that Kit takes and prefer something more opinionated like Biff. I'd love to hear your feedback if you do end up trying out Biff.

For some common tasks, neil is also an option.

Let's setup a basic project that includes a logger. I think the nicest way to get a new project up is with one of the tools that Borkdude has created, called neil. If you have this installed, just run the following in an empty directory:

When I see legit anger and frustration in these comments, I also think about the newcomers who might be turned off by the funky syntax just to generate a template. That said, my solution to this wasn't to add another complaint to the thread, but to add the neil new command to solve this problem for tools.deps going forward.

There is also neil which offers some features to make working with deps.edn a little easier.

(criterium does not work here yet b.t.w., but it probably will be working soon)

criterium, specifically the quick-bench function, will actually run multiple samples an provide a mean runtime (as well as other useful stats) so you can get an idea of what a jit'd warmed up performance looks like. time is great in a pinch, but you end up needing to run it multiple times to ensure optimizations are kicking and and other artifacts (like gc) aren't throwing the results.

I'm going to leave tooling out of this and run everything through a repl on the command line right from the jar. One other thing I want to do is include the incredible criterium library so we can profile. I'm deliberately including criterium separately like this because you shouldn't have a dev-time tool like criterium in an uberjar. And knowing how to easily combine other jars with your real production jar can be very helpful. I grabbed the jar from my .m2 cache.

I am just going to leave this here - https://github.com/hugoduncan/criterium

where crit is criterium. As you can see, you're spending most of your time in the seq transformation part.

It's better to benchmark with something like criterium. time is a bit inaccurate. Though, if it's really 15 seconds, I guess will not be that big of a difference

>>> One of Clojure's biggest weaknesses in practice is that breaking in to those functional structures to figure out where the time is being spent or to debug them is harder than in other languages. This is a natural trade-off of developing a terse and powerful language.

Not that hard if you use something like YourKit. There's also a quite good Clojure library https://github.com/hugoduncan/criterium .

Criterium (the benchmarking library used here) uses multiple runs to obtain tighter bounds on amortized performance, as well as techniques to amortize the effects of garbage collection and JIT compilation. See https://github.com/hugoduncan/criterium for a brief overview, as well as links to the pitfalls and statistical techniques involved in JVM benchmarking.