One of the hardest question to ask on a linux platform: how much memory does my application use. This is mostly because Linux is amazingly efficient when it comes to memory usage and management. But it comes with a price - readability on how much memory your application really uses.

During this advanced presentation, we will talk about virtual spaces, MMUs, mmap(), shared, resident and virtual memory and how it all fits together on your servers.

Afterwards, you will be one of few who can read tools like "top" and "free" and really understand what's going on.


Comments are closed.

Anonymous at 14:08 on 9 Jun 2018

The talk was pretty clear in it's explanations and examples, and nicely paced. Only thing is that from the disclaimers and indicated tech level I expected it to be a bit more in depth, and summarizing these basics in a much shorter time.

Good talk.

Hans Dubois at 14:51 on 9 Jun 2018

Great talk, nice way of making a complex thing really simple. Good job!

Nice talk, theory explained in a very clear way so that we can work with it.

Onno Marsman at 13:53 on 11 Jun 2018

I did not feel like this was an advanced talk, only basic computer knowledge was needed beforehand which can easily be expected from anyone attending.
I did learn some expected stuff about the tools to read memory usage, but I also expected to learn something about what to do with this information in certain circumstances.

Really enjoyable talk. Concepts well explained. Good slides clear slides.

My only tip for improvement...
I still felt at the end a little unsure how to actually read top to work out what was going on memory wise. I would have liked a final review of the top command output, maybe explicitly highlighting parts of it, as a reminder the the important information with regard to memory usage.

Great talk.

Good clear information presented in a nice manner.

I would suggest giving some more suggestions on how to interpret/use top (and other tools) "in real life". How to switch to some relevant views and what certain numbers *might* be telling you.
It might have been said, but some examples using some screenshots to make it a bit more concrete would help.