Good list of things to keep in mind when thinking about performances. Of course, always measure using a profiler when you want to be really sure.

Interesting way to approximate how loaded a system is.

Interesting tale and exploration on how a change in includes impacted cache misses. This is sneaky (and solved with more recent compilers).

The claim is huge. The story doesn't quite say how much is really about Elixir and how much from the revised architecture. That being said, going for something like Elixir has definitely an impact on the architecture... could it be that it pushes for better patterns?

Another partial quote which led to misunderstanding. One should indeed think about performances early on.

Obvious advice perhaps, but so easily forgotten somehow...

OK, this could be big for Python. Let's see how they execute this plan. It carries some risks as well, but they seem well aware of them.

Interesting optimization on this somewhat common data structure.

Unsurprisingly, it's not as simple as it sounds. Type hints in Python can be used for various reasons but performances is rarely the main motives. It'd need other adjustments to the runtime. People are working on it, and this article is an interesting dive on how things work under the hood.

This compilation technique brings very interesting results. Hopefully should find its way in some JIT compilers.

Interesting research turning to genetic algorithms to optimize bytecode handler dispatchers.

Deep dive on a proper benchmarking and implementation for 1M task on the Erlang runtime. Clearly the previous benchmark had room for improvements.

Nice and thorough workshop on vectorization, where it comes from, what it can do and how you can write code which is easier to vectorize for the compiler.

Doesn't give the whole picture (memory isn't the only important parameter) but interesting results nonetheless. A few surprises in there, Java and C# do much better than one might assume for instance.

Interesting take. Will it lead to paying more attention to performance in software? Will it be the rise of the specialized CPUs? Time will tell.

Good explanation of how flame graphs are produced and how to read them. Gives a few tips on what to look for to optimize.

Interesting exploration on the performance of SSDs regarding write patterns. Turns out sequential IO is still a thing, just for a different reason than with good old HDDs.

Very interesting to see that move to owned hardware... turns out that not only the invoice is smaller in their case but the performances are much better as well.

Nice set of tips, I knew a few but not all of them. The discussion around CTEs is interesting.

Nice exploration of false sharing on performances in several hardware scenarii. A couple of surprises along the way.