Datasets:
willtheorangeguy
/
2016-Go-Time-Transcripts

Dataset card Data Studio Files
xet
 Community
text
stringlengths
0
1.82k
[2612.82 --> 2613.16] fact that
[2613.16 --> 2613.60] they're using
[2613.60 --> 2614.12] RocksDB.
[2614.48 --> 2615.08] There's a lot
[2615.08 --> 2615.38] of people
[2615.38 --> 2615.80] using that
[2615.80 --> 2615.98] now.
[2616.14 --> 2616.40] There's a
[2616.40 --> 2616.92] Mongo
[2616.92 --> 2618.82] Rocks was
[2618.82 --> 2619.22] out not
[2619.22 --> 2619.54] too long
[2619.54 --> 2619.96] ago.
[2622.22 --> 2622.90] One of our
[2622.90 --> 2623.42] other favorites,
[2623.56 --> 2624.20] CockroachDB,
[2624.62 --> 2625.18] they're using
[2625.18 --> 2626.28] RocksDB under
[2626.28 --> 2626.78] the covers,
[2627.02 --> 2627.50] unless they've
[2627.50 --> 2627.98] changed by
[2627.98 --> 2628.32] now, but I
[2628.32 --> 2628.56] think they're
[2628.56 --> 2629.00] still using
[2629.00 --> 2629.20] it.
[2630.32 --> 2630.96] RocksDB
[2630.96 --> 2631.46] actually comes
[2631.46 --> 2631.64] out of
[2631.64 --> 2631.96] Facebook.
[2633.20 --> 2633.64] I definitely
[2633.64 --> 2634.08] just want to
[2634.08 --> 2634.58] shout out to
[2634.58 --> 2635.06] Scott and
[2635.06 --> 2635.60] the team at
[2635.60 --> 2636.38] Netflix for
[2636.38 --> 2637.16] such a nice
[2637.16 --> 2637.66] and thorough
[2637.66 --> 2638.14] write-up.
[2638.14 --> 2639.08] I know
[2639.08 --> 2639.76] Scott's been
[2639.76 --> 2640.58] dragging the
[2640.58 --> 2640.96] people who
[2640.96 --> 2641.46] will listen,
[2641.86 --> 2642.88] kicking and
[2642.88 --> 2643.42] screaming into
[2643.42 --> 2644.06] the Go world.
[2644.58 --> 2645.00] Even though
[2645.00 --> 2645.62] they're a
[2645.62 --> 2646.12] Java-heavy
[2646.12 --> 2647.18] shop, they
[2647.18 --> 2647.70] do have a
[2647.70 --> 2648.04] lot of Go
[2648.04 --> 2648.50] behind the
[2648.50 --> 2648.98] scenes there.
[2649.08 --> 2649.34] They just
[2649.34 --> 2649.76] don't talk
[2649.76 --> 2650.24] about it a
[2650.24 --> 2650.40] lot.
[2651.78 --> 2653.46] I remember
[2653.46 --> 2653.94] seeing some
[2653.94 --> 2654.10] of the
[2654.10 --> 2654.54] performance
[2654.54 --> 2654.92] metrics.
[2655.12 --> 2655.54] There was
[2655.54 --> 2656.12] something in
[2656.12 --> 2656.44] the neighborhood
[2656.44 --> 2657.68] of 2 million
[2657.68 --> 2658.92] requests per
[2658.92 --> 2659.46] second, but I
[2659.46 --> 2659.76] think that
[2659.76 --> 2661.32] wasn't fully
[2661.32 --> 2661.82] accurate because
[2661.82 --> 2662.28] that wasn't
[2662.28 --> 2662.84] wired up to
[2662.84 --> 2663.42] back ends.
[2663.58 --> 2663.90] I know when
[2663.90 --> 2664.84] it was all
[2664.84 --> 2665.38] said and done,
[2665.46 --> 2665.72] the whole
[2665.72 --> 2666.60] system was
[2666.60 --> 2667.84] something in
[2667.84 --> 2668.20] the neighborhood
[2668.20 --> 2669.18] of 20 or
[2669.18 --> 2671.42] 25,000 inserts
[2671.42 --> 2672.04] per second.
[2672.22 --> 2673.14] But still, the
[2673.14 --> 2673.48] amount of
[2673.48 --> 2674.12] performance that
[2674.12 --> 2674.42] we're getting
[2674.42 --> 2675.04] out of this
[2675.04 --> 2676.78] Go proxy is
[2676.78 --> 2678.06] awesome.
[2678.92 --> 2679.66] We'll link to
[2679.66 --> 2680.22] that in the
[2680.22 --> 2680.82] show notes too
[2680.82 --> 2681.26] because that is
[2681.26 --> 2681.74] an interesting
[2681.74 --> 2682.16] read.
[2682.64 --> 2683.24] Especially if
[2683.24 --> 2683.48] you're not