We all have been fooled! They told us that automatic memory management will solve all our problems. In managed worlds like .NET, JVM and others there is no memory leak, they said. You will never need to think about freeing memory manually. There is no need to think about memory management at all, they said. And they all lied!

Automatic memory management is just an abstraction. But like any other abstraction, it is convenient and nice and… it eventually leaks. In the most unpredictable and unpleasant way. No matter what platform or language you use, you are probably a victim of those lies. And while in many popular use cases they just work, I would like to show you some deeper insight.

In this talk, I would like to open your eyes on some low-level stuff that is going inside your computers and servers that execute your production code. Things that influence your code performance. And design patterns that will allow you to write more memory-aware code.

Takeaways:
* automatic memory management is not a silver-bullet - it has its own caveats that we should be aware of
* there are design patterns like Data-Oriented Design that try to leverage memory-awareness and they are perfectly usable in managed runtimes
* not so many people are even aware of how memory works (CPU caches, cache lines, DRAM) while it is really crucial in a performant code to know such details