home.social

#flamegraphs — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #flamegraphs, aggregated by home.social.

  1. And then a nice presentation by Vinicius Grippa: Bringing #Flamegraphs to #MySQL Query Optimization. (github.com/vgrippa/myflame)
    I love his brazilian accent... 🥰

  2. Ah, yes, yet another clash of the titans: Flame Graphs, Tree Maps, and #Sunbursts battling it out in a death match no one asked for, but everyone pretends to care about 🤷‍♂️. With more buzzwords than a Silicon Valley startup's pitch deck, this 2017 throwback is as relevant as a floppy disk in a cloud computing world 🌩️💾.
    brendangregg.com/blog/2017-02- #FlameGraphs #TreeMaps #TechBuzzwords #2017Throwback #HackerNews #ngated

  3. Ah, yes, yet another clash of the titans: Flame Graphs, Tree Maps, and #Sunbursts battling it out in a death match no one asked for, but everyone pretends to care about 🤷‍♂️. With more buzzwords than a Silicon Valley startup's pitch deck, this 2017 throwback is as relevant as a floppy disk in a cloud computing world 🌩️💾.
    brendangregg.com/blog/2017-02- #FlameGraphs #TreeMaps #TechBuzzwords #2017Throwback #HackerNews #ngated

  4. Ah, yes, yet another clash of the titans: Flame Graphs, Tree Maps, and #Sunbursts battling it out in a death match no one asked for, but everyone pretends to care about 🤷‍♂️. With more buzzwords than a Silicon Valley startup's pitch deck, this 2017 throwback is as relevant as a floppy disk in a cloud computing world 🌩️💾.
    brendangregg.com/blog/2017-02- #FlameGraphs #TreeMaps #TechBuzzwords #2017Throwback #HackerNews #ngated

  5. Ah, yes, yet another clash of the titans: Flame Graphs, Tree Maps, and #Sunbursts battling it out in a death match no one asked for, but everyone pretends to care about 🤷‍♂️. With more buzzwords than a Silicon Valley startup's pitch deck, this 2017 throwback is as relevant as a floppy disk in a cloud computing world 🌩️💾.
    brendangregg.com/blog/2017-02- #FlameGraphs #TreeMaps #TechBuzzwords #2017Throwback #HackerNews #ngated

  6. How to use #flamegraphs for #performance #profiling

    runbooks.gitlab.com/tutorials/

    Off-CPU Analysis - by Brendan Gregg:
    brendangregg.com/offcpuanalysi

    - On-CPU: where threads are spending time running on-CPU
    - Off-CPU: where time is spent waiting while blocked on I/O, locks, timers, paging/swapping, etc.

    #Testing #Perf #DataViz #DataVisualization #Flamegraph

  7. How to use #flamegraphs for #performance #profiling

    runbooks.gitlab.com/tutorials/

    Off-CPU Analysis - by Brendan Gregg:
    brendangregg.com/offcpuanalysi

    - On-CPU: where threads are spending time running on-CPU
    - Off-CPU: where time is spent waiting while blocked on I/O, locks, timers, paging/swapping, etc.

    #Testing #Perf #DataViz #DataVisualization #Flamegraph

  8. How to use #flamegraphs for #performance #profiling

    runbooks.gitlab.com/tutorials/

    Off-CPU Analysis - by Brendan Gregg:
    brendangregg.com/offcpuanalysi

    - On-CPU: where threads are spending time running on-CPU
    - Off-CPU: where time is spent waiting while blocked on I/O, locks, timers, paging/swapping, etc.

    #Testing #Perf #DataViz #DataVisualization #Flamegraph

  9. How to use #flamegraphs for #performance #profiling

    runbooks.gitlab.com/tutorials/

    Off-CPU Analysis - by Brendan Gregg:
    brendangregg.com/offcpuanalysi

    - On-CPU: where threads are spending time running on-CPU
    - Off-CPU: where time is spent waiting while blocked on I/O, locks, timers, paging/swapping, etc.

    #Testing #Perf #DataViz #DataVisualization #Flamegraph

  10. How to use #flamegraphs for #performance #profiling

    runbooks.gitlab.com/tutorials/

    Off-CPU Analysis - by Brendan Gregg:
    brendangregg.com/offcpuanalysi

    - On-CPU: where threads are spending time running on-CPU
    - Off-CPU: where time is spent waiting while blocked on I/O, locks, timers, paging/swapping, etc.

    #Testing #Perf #DataViz #DataVisualization #Flamegraph

  11. “Hands up if you’re using #flamegraphs ” - 80% of the room #sre-next

  12. “Hands up if you’re using #flamegraphs ” - 80% of the room #sre-next

  13. “Hands up if you’re using #flamegraphs ” - 80% of the room #sre-next

  14. “Hands up if you’re using #flamegraphs ” - 80% of the room #sre-next

  15. “Hands up if you’re using #flamegraphs ” - 80% of the room #sre-next

  16. The best software is the one, where you can't decide if something is a cool or a terribly ugly idea.
    github.com/namhyung/uftrace
    #linux, #ftrace but in userspace, #flamegraphs

  17. The best software is the one, where you can't decide if something is a cool or a terribly ugly idea.
    github.com/namhyung/uftrace
    #linux, #ftrace but in userspace, #flamegraphs

  18. The best software is the one, where you can't decide if something is a cool or a terribly ugly idea.
    github.com/namhyung/uftrace
    , but in userspace,

  19. The best software is the one, where you can't decide if something is a cool or a terribly ugly idea.
    github.com/namhyung/uftrace
    #linux, #ftrace but in userspace, #flamegraphs

  20. Brendan Gregg does some great talks. Just watched this one on #eBPF and #flamegraphs: youtube.com/watch?v=HKQR7wVapg

    Could understand about half but very interesting nonetheless

  21. Brendan Gregg does some great talks. Just watched this one on and : youtube.com/watch?v=HKQR7wVapgk

    Could understand about half but very interesting nonetheless

  22. Brendan Gregg does some great talks. Just watched this one on #eBPF and #flamegraphs: youtube.com/watch?v=HKQR7wVapg

    Could understand about half but very interesting nonetheless

  23. @richardstartin Perhaps it’s just me but I find #flamegraphs less useful as the profile grows in size and dominating effects weaken. Then it’s back to #JMC tabular data (usually itable stubs!) which I combine with a little #LogCompilation parser to get the JIT’s view on what’s happening.

  24. @richardstartin Perhaps it’s just me but I find #flamegraphs less useful as the profile grows in size and dominating effects weaken. Then it’s back to #JMC tabular data (usually itable stubs!) which I combine with a little #LogCompilation parser to get the JIT’s view on what’s happening.

  25. @richardstartin Perhaps it’s just me but I find #flamegraphs less useful as the profile grows in size and dominating effects weaken. Then it’s back to #JMC tabular data (usually itable stubs!) which I combine with a little #LogCompilation parser to get the JIT’s view on what’s happening.

  26. @richardstartin Perhaps it’s just me but I find #flamegraphs less useful as the profile grows in size and dominating effects weaken. Then it’s back to #JMC tabular data (usually itable stubs!) which I combine with a little #LogCompilation parser to get the JIT’s view on what’s happening.

  27. @richardstartin Perhaps it’s just me but I find #flamegraphs less useful as the profile grows in size and dominating effects weaken. Then it’s back to #JMC tabular data (usually itable stubs!) which I combine with a little #LogCompilation parser to get the JIT’s view on what’s happening.

  28. The example bt(5)/btrace(8) scripts are now installed in #OpenBSD -current (missed with 7.1):

    • kprofile .bt (save kernel stackframes & produce flamegraphs)
    • runqlat .bt (measure the latency of the scheduler runqueues).

    You can generate #flamegraphs with Brendan Gregg's FlameGraph script. :flan_thumbs:​

    github.com/brendangregg/FlameG

  29. The example bt(5)/btrace(8) scripts are now installed in #OpenBSD -current (missed with 7.1):

    • kprofile .bt (save kernel stackframes & produce flamegraphs)
    • runqlat .bt (measure the latency of the scheduler runqueues).

    You can generate #flamegraphs with Brendan Gregg's FlameGraph script. :flan_thumbs:​

    github.com/brendangregg/FlameG