GopherCon 2021: Felix Geisendörfer - Go Profiling and Observability from Scratch

Поделиться
HTML-код
  • Опубликовано: 9 июл 2024
  • This talk is for anybody who is interested in reducing costs and latency, or debugging problems such as memory leaks, infinite loops, performance regressions, etc.
    We'll begin by establishing a simple but useful mental model for the Go runtime and explain how Go differs from other compiled languages. This will serve as a foundation to understand the built-in CPU, Memory, Block, Mutex, and Goroutine Profilers as well as the Runtime Tracer.
    Additionally, the presentation will cover eBPF, Linux Perf, and Delve. By the end, viewers should walk away with a solid understanding of the various tools one can use to optimize and debug Go applications.
  • НаукаНаука

Комментарии • 11

  • @iKayos
    @iKayos 2 года назад +7

    This is by far the most informative golang video I have ever come across.

  • @JaihindhReddy
    @JaihindhReddy 2 года назад +1

    This talk is chock-full of good information about profiling, especially experiential information. Thanks a lot Felix!

  • @jayleejw1801
    @jayleejw1801 Месяц назад

    Thanks for this video. It helps me realise I really not interested in such details about golang 😂

  • @hamzadlm6625
    @hamzadlm6625 Год назад

    what is wonderful presentation!

  • @WomboBraker
    @WomboBraker Год назад

    Holy fuck how did i stumble upon to this gem! Amazing!!!!

  • @amirehsandar6782
    @amirehsandar6782 Год назад

    Good stuff

  • @XiGlenGu
    @XiGlenGu Год назад

    Has anyone figured out the real cause of the json-marshal acceleration?

  • @vinodrajj
    @vinodrajj Год назад

    Can this PPT is sharable ?

  • @chiahsinglin6675
    @chiahsinglin6675 Год назад

    Hope the voice could be more louder

  • @nickandrievsky5705
    @nickandrievsky5705 5 месяцев назад

    Nice video. You just drop the ball by being unable to understand results of your own test application behavior.

  • @AlexanderDemin
    @AlexanderDemin Год назад

    The “else” based way is by far the ugliest and most confusing and must be avoided :-)