You can try #architecture as well.

Thanks, will post there too.

I read http://shop.oreilly.com/product/0636920033158.do years ago to understand why everyone was talking about Microservices, it delves into DDD/Bounded Contexts

It's a well written book.

Lot's of concerns there. Personnaly I find it helpfull the think in -illities to find the best solution. Like deployability, evolvability, scalibility, testability, how does extracting some code to a deplyable unit affect those, and which of those are more important.

Much like https://www.thoughtworks.com/books/building-evolutionary-architectures

I will look at it, thanks!

That's a fair point. I just want to do this for fun though. Optimizing Clojure code has become my favourite pass time.

I don't do Clojure at work. All of this is my hobby.

Take a look at https://github.com/tonsky/persistent-sorted-set

There is also some cool stuff here https://github.com/tonsky/icfpc2019-rust

I build https://graphql.gklijs.tech/results/graphql-servers/transactions-per-second but Clojure is already the best. That being said, happy for any pr. Still waiting for subscriptions to hit the rust GraphQL server to add rust.

At least, there's some explanation: https://benchmarksgame-team.pages.debian.net/benchmarksgame/sometimes-people-just-make-up-stuff.html#maintenance-burden

I Googled and found the history of that. Is there another?

I’ve had some conversations with him. I respect his desire to spend his time how he wants.

I am sure he has spent many many hours fielding requests from various people to replace which benchmark program is used, or to remove ones because they don't follow the game rules (I have asked about a few programs myself years ago, when actively writing programs for the site for Clojure, and trying to understand how other programs worked -- he often responded in a timely fashion).

His advice is sound: If you want a web site that publishes results for a particular set of languages, create one.

That's cool. They are great as references.

the versions that were posted that I worked on are all at https://github.com/clojure/test.benchmark

iirc, a lot of the "how to run" stuff in there is likely to be old and/or kind of bespoke

and/or broken

if you want to see a lot of funky clojure perf tricks, they're all in there :)

Yeah, mainly interested in the funky tricks, 🙂

fix reflection, fix boxing, use primitives, use deftype/definterface, use array packing when you can't pass enough primitives, primitive constants, etc

but for most of the places I did the tricks, in real life, I would just write the damn loop in Java

a lot of my interim revisions and notes are squirrelled away in the archive directory

pidigits is probably the worst hack, although I merely polished that one - it uses clojure.asm (NOT a public api) to just write, compile, and load bytecode directly

The pidigits one sounds like cheating to me, 🙂

iirc there was really only one reason to do so, something to do with marking native methods, which I made a ticket for but not sure ever got fixed.

oh, that's totally cheating the spirit

I did not get the array packing trick.

you can only pass 4 primitives in a function with primitive type hints

for the rare case you need more, you can pack them in a mutable Java array

in general, mutable Java arrays are the swiss army knife of Clojure hacks :)

Oh, cool trick. 👍

assuming you're single-threaded, they are very memory efficient, very fast, stateful references

and hotspot can do wonders....