text stringlengths 0 1.49k |
|---|
[2719.66 --> 2720.54] It's got the |
[2720.54 --> 2721.14] Go Tracer |
[2721.14 --> 2722.64] in it and |
[2722.64 --> 2723.32] he walks you |
[2723.32 --> 2723.64] through how |
[2723.64 --> 2724.38] to use it |
[2724.38 --> 2725.60] from start |
[2725.60 --> 2726.44] to finish and |
[2726.44 --> 2727.36] it's awesome. |
[2727.60 --> 2728.00] I love the |
[2728.00 --> 2728.66] Go Tracer so |
[2728.66 --> 2729.66] much but |
[2729.66 --> 2731.30] it's severely |
[2731.30 --> 2732.38] lacking in |
[2732.38 --> 2733.00] documentation. |
[2734.02 --> 2734.64] Severely |
[2734.64 --> 2735.20] lacking. |
[2735.30 --> 2735.82] Tell us what |
[2735.82 --> 2736.50] the Go Tracer |
[2736.50 --> 2736.94] does. |
[2737.70 --> 2738.38] I actually |
[2738.38 --> 2739.04] looked to see |
[2739.04 --> 2739.70] if that was |
[2739.70 --> 2740.54] explained anywhere |
[2740.54 --> 2741.46] and it really |
[2741.46 --> 2741.92] isn't. |
[2742.44 --> 2742.96] It isn't. |
[2743.02 --> 2743.48] Go Tracer |
[2743.48 --> 2745.08] allows you to |
[2745.08 --> 2746.60] instrument your |
[2746.60 --> 2748.00] Go applications |
[2748.00 --> 2749.44] and capture |
[2749.44 --> 2753.42] performance metrics |
[2753.42 --> 2754.84] that you can |
[2754.84 --> 2755.80] then put |
[2755.80 --> 2756.46] through |
[2756.46 --> 2757.86] different |
[2757.86 --> 2758.76] tracing tools. |
[2759.26 --> 2759.66] Go Tracer |
[2759.66 --> 2760.62] is one of |
[2760.62 --> 2760.86] them. |
[2762.32 --> 2762.88] And it |
[2762.88 --> 2763.60] lets you |
[2763.60 --> 2764.10] see, |
[2764.46 --> 2765.10] for example, |
[2766.26 --> 2767.12] what you're |
[2767.12 --> 2767.64] spending most |
[2767.64 --> 2768.20] of your CPU |
[2768.20 --> 2769.18] time on or |
[2769.18 --> 2769.76] where you're |
[2769.76 --> 2770.40] allocating the |
[2770.40 --> 2771.02] most memory. |
[2772.14 --> 2772.82] The better |
[2772.82 --> 2773.32] tools are |
[2773.32 --> 2774.02] visual and |
[2774.02 --> 2775.08] you can click |
[2775.08 --> 2775.64] on things |
[2775.64 --> 2776.08] and find |
[2776.08 --> 2776.46] out, |
[2776.54 --> 2777.48] you know, |
[2777.56 --> 2778.52] because the |
[2778.52 --> 2778.94] graph is |
[2778.94 --> 2779.30] bigger, |
[2779.86 --> 2780.46] this is where |
[2780.46 --> 2780.94] I'm spending |
[2780.94 --> 2781.48] more of my |
[2781.48 --> 2781.88] time and |
[2781.88 --> 2782.36] you can drill |
[2782.36 --> 2783.34] in and get |
[2783.34 --> 2783.72] all the way |
[2783.72 --> 2784.18] down to the |
[2784.18 --> 2784.90] function level. |
[2785.44 --> 2785.60] All right, |
[2785.66 --> 2786.40] this code |
[2786.40 --> 2787.30] takes more |
[2787.30 --> 2787.68] time than |
[2787.68 --> 2788.34] anything else |
[2788.34 --> 2789.26] or I'm |
[2789.26 --> 2789.74] calling this |
[2789.74 --> 2790.44] one function |
[2790.44 --> 2791.32] so many |
[2791.32 --> 2791.90] times that |
[2791.90 --> 2792.38] it's taking |
[2792.38 --> 2792.90] all of my |
[2792.90 --> 2793.64] CPU time. |
[2793.80 --> 2794.06] So you |
[2794.06 --> 2794.90] can drill |
[2794.90 --> 2795.44] into your |
[2795.44 --> 2796.00] app and |
[2796.00 --> 2797.34] find performance |
[2797.34 --> 2798.08] issues that |
[2798.08 --> 2798.36] way. |
[2799.36 --> 2799.72] Cool. |
[2799.72 --> 2801.22] So it's |
[2801.22 --> 2802.24] a good |
[2802.24 --> 2802.54] video. |
[2802.72 --> 2803.70] Go watch |
[2803.70 --> 2803.86] that. |
[2804.46 --> 2804.90] I do |
[2804.90 --> 2805.56] have one |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.