my talk at linux piter 2016

On performance analyzing again:Gathering and visualizing flamegraphs in

realtime in Linux environment

Alex Chistyakov, DataArt

Linux Piter 2016, Russia, SPb.

Alex Chistyakov, DataArt Gathering and visualizing flamegraphs in realtime 1 / 51

Who I am (very quickly)


• Senior SW Developer @ DataArt

• More than 18 years of professional experience

• Researcher @ ISST Lab, ITMO

• Used to be a DevOps Engineer and still probably am

• Can’t quit making presentations w/lots of bullets (that’sterrible, I know)

Performance optimization is not that hard


Ever heard of a ’comfort zone’?


• It’s crucial to be out of it to learn something new




• So I made this presentation in TeX





• With lots of bullets, you know






• Because I’m not ready yet to leave my comfort zoneentirely






• Because I’m not ready yet to leave my comfort zoneentirely

• Damn, TeX seems to be my new comfort zone ;(

Okay, flashback to LP 2015 (w/no bullets)


Fast-forward to 2016


Brendan Gregg declared Linux DTrace-complete!

A great step forward for mankind...


...but I’m a cat

So, what is this all about?


• Modern GNU/Linux




• A web application





• Collecting flamegraphs





• Collecting flamegraphs

• Visualizing collected flamegraphs

Okay, but what are these flame... things?


Did you attend LP 2015?

Doing flamegraphs in 2016 is extremely easy


A hicker needs good boots


So, we need a language


The obvious choice


Why Lisp?


• Homoiconicity

Why Lisp?


• Homoiconicity

• Macros

Why Lisp?


• Homoiconicity

• Macros

• Immutability (?)

Why Lisp?


• Homoiconicity

• Macros

• Immutability (?)

• Lambdas

But that was not too democratic, so...


...what about Golang?

Unfortunately, Golang loses


• Way too modern (uses design ideas from 1970s while Lispwas born in 1958)




• Not functional enough (as in ’functional programming’)




• Not functional enough (as in ’functional programming’)

• Targets Java 1.2 and PHP 4.x market share (designed forapes not humans)

Runtime matters!


• Static linking is a must

Runtime matters!



• Decent GC is a must

Runtime matters!




• Resulting files should not be too big

Runtime matters!




• Resulting files should not be too big

• Let’s consider measureable things only

So, Lisps then


• Common Lisp

• Scheme

Common Lisp


Statically linked file is over 30Mb (Golang does around 8Mb)

Scheme


Is minimalist by design (way too minimalist I’d say)

So, no boots then?


Nim to the rescue!


Nim (formerly Nimrod)

Nim: the good parts


• Strong typing

Nim: the good parts


• Strong typing

• Static typing

Nim: the good parts


• Strong typing

• Static typing

• Homoiconicity

Nim: the good parts


• Strong typing

• Static typing

• Homoiconicity

• Macro system (hygienic)

Nim: the good parts


• Strong typing

• Static typing

• Homoiconicity


• Immutability

Nim: the good parts


• Strong typing

• Static typing

• Homoiconicity


• Immutability

• Templates (generics)

Nim: runtime goodness


• Uses C as an IR



• Uses C as an IR

• Per thread GC (as in Erlang)



• Uses C as an IR

• Per thread GC (as in Erlang)

• Statically linked files < 1Mb (not stripped)

Project Kaldur


• Means ’cold’ in Faroese

• Because it’s quite cold now

• https://github.com/alexclear/kaldur

https://github.com/alexclear/kaldur

Project Kaldur


• Is live at http://185.37.61.240:5000

• Has a TODO list on Github

• Has an issues list on Github

http://185.37.61.240:5000

Conclusions


• TeX is great!

• Nim is great too!

• Flamegraphs are great!

• Linux is great!

• Open source projects are great!

Questions, please?


• Why FP?

• Why Linux?

• ...?

So long, and thanks for all the fish


• [email protected]

• https://telegram.me/lhommequipleure

mailto:[email protected]

https://telegram.me/lhommequipleure

my talk at linux piter 2016

Technology