Two Go Programs, Three Different Profiling Techniques - Dave Cheney

Поділитися
Вставка
  • Опубліковано 5 гру 2024

КОМЕНТАРІ • 40

  • @mayurgaitonde5069
    @mayurgaitonde5069 4 роки тому +11

    Dave Cheney is the unsung hero of the Go community.

  • @tuliogomes7210
    @tuliogomes7210 2 роки тому +6

    Amazing talk! This guy has the ability to present such complex topics in a simple way!

  • @13TheGUNNER
    @13TheGUNNER 2 роки тому +3

    Amazing presentation! I wonder how a software engineer can think of such visual explanations! Hats off.

  • @AndreiDinTheHouse
    @AndreiDinTheHouse 2 роки тому +1

    Amazing. I got a bit stuck at "buffer yourself". I saw this presentation shortly after it was uploaded in 2019 and since then it's become my pet peeve in code reviews as well as sortof catchphrase. "Go buffer yourself".

  • @ИгорьАлексеев-э9к
    @ИгорьАлексеев-э9к 2 роки тому +2

    Clear message, clear structure, easy to understand, thank you

  • @MrAndrewtux
    @MrAndrewtux 2 роки тому +2

    Great talk ! Also I am novice of go and I can understand! Thanks

  • @amitbhaira2492
    @amitbhaira2492 4 роки тому +7

    Amazing. Thank you so much for delivering such great presentation.

  • @qishuai3041
    @qishuai3041 2 роки тому +1

    great presentation. Thanks

  • @Bagasl
    @Bagasl 2 роки тому +1

    One of the best talks ever. Thank you. Your blog is amazing too, love it

  • @blank001
    @blank001 3 роки тому

    Great talk man, instead of just showing slides and talking you are showing all the nuts and bolts that makes the program what it is.

  • @jfrankogramos6620
    @jfrankogramos6620 5 років тому +9

    nice I love Go

  • @srgpip
    @srgpip 4 роки тому +2

    Thank you for providing a great presentation.

  • @gl3nda96
    @gl3nda96 2 роки тому +1

    Amazing talk and great explanation!

  • @kamal-xd7id
    @kamal-xd7id 4 роки тому +1

    Learned a lot from this great talk.

  • @barsvelioglu2276
    @barsvelioglu2276 Рік тому

    Absolutely amazing talk. Thanks

  • @zeinfahrozi7828
    @zeinfahrozi7828 4 роки тому +1

    Great talk. I learn something new about Go

  • @vaskir3695
    @vaskir3695 3 роки тому

    Great talk, especially switching to tracing when cpu profiling gave no clue.

  • @C0DE8
    @C0DE8 4 роки тому +1

    Awesome high quality presentation!!! Thanks a lot!

  • @macfhlannchadharonan4668
    @macfhlannchadharonan4668 4 роки тому +1

    Learnt plenty thanks very much, brilliant presentation!

  • @MrBlanky666
    @MrBlanky666 3 роки тому +1

    Awesome, thanks!

  • @trungthanhbp
    @trungthanhbp Місяць тому

    thank you for saved me

  • @LuadoO
    @LuadoO 3 роки тому +1

    I did not get it fully, why on the first part, when Dave moves the buffer declaration to file scope, that avoids that escaping of the buffer to the heap. Why did it escape to the heap? I watched his explanation over and over, but it's still not 100% for me.

    • @LuadoO
      @LuadoO 3 роки тому

      Also, brilliant presentation!!!

    • @sebas11tian
      @sebas11tian 3 роки тому

      My understanding is that slices work as pointers to a subsection of the underlying array. Because the declaration is only invoked once, there are no memory allocation requests and therefore you are recycling the same memory byte as opposed to asking the OS to give you a new piece of the stack every time you call the function.

    • @sebas11tian
      @sebas11tian 3 роки тому

      The compiler, therefore knows what will happen to the array in the stack once the function is closed and therefore it can declare that keeping it in the stack frame is safe and does not require going off to the heap.

  • @Orww
    @Orww 5 років тому +2

    great talk

  • @cal1686
    @cal1686 4 роки тому

    This is bookmark worthy

  • @kalasmournrex1470
    @kalasmournrex1470 2 роки тому

    Nice talk. It's kind of infuriating that go doesn't just inline readByte and avoid the heap allocation, though.

  • @LaTekapo
    @LaTekapo 4 роки тому +2

    can u share code with us?

  • @karlpokus
    @karlpokus 5 років тому +2

    Thanks!

  • @xuyangsun7948
    @xuyangsun7948 2 роки тому

    In my mac air m1,mode row's performance is more better than mode workers, no matter how many workers used

  • @DavidAlsh
    @DavidAlsh 2 роки тому

    When you started talking about thousands of cores and calculating each row or pixel on a core - I thought you were going to dive into GPU programming 🤣

  • @andherium
    @andherium 3 роки тому

    What were the 3 different profiling techniques ?
    - pprof
    - trace
    - ??

    • @LuadoO
      @LuadoO 3 роки тому +1

      Memory, CPU and Trace ma dude

  • @kiselkisel3463
    @kiselkisel3463 2 роки тому

    Somebody get me link on source code

  • @TheMrKeksLp
    @TheMrKeksLp 4 роки тому

    Unix user "dfc" hehe

  • @sm5172
    @sm5172 3 роки тому +1

    Excellent talk, enjoyed it very much! Please, more talks like these in 2021 instead of the political social justice BS you decided to sneak into GopherCon 2020.