text stringlengths 0 1.8k |
|---|
[1354.66 --> 1363.28] And so it'll allow you to fail at a much earlier stage, potentially even on a developer's local machine rather than once it gets to production. |
[1363.28 --> 1365.72] That's exactly what we've been using. |
[1365.72 --> 1373.52] We've developed a serverless package to easily deploy serverless functions on AWS. |
[1374.34 --> 1376.08] And that's basically what we used. |
[1376.70 --> 1377.84] So it's kind of useful. |
[1378.20 --> 1384.04] So sometimes you have like the names, they are forbidden characters and we just do it. |
[1384.46 --> 1389.52] We use these validations to avoid, to fail early. |
[1389.52 --> 1390.16] Yeah. |
[1390.72 --> 1390.98] Okay. |
[1391.48 --> 1393.86] So, yeah, there's a lot to explore here. |
[1394.20 --> 1395.96] I really, really like you. |
[1396.02 --> 1398.08] I have to say there's like so many great things about it. |
[1398.44 --> 1402.68] And it makes like not having the right inputs, not having the right values. |
[1402.74 --> 1404.92] It just really helps. |
[1405.08 --> 1408.58] Like the compiler errors for queue are really good. |
[1408.90 --> 1411.40] And they steer you like in the right direction. |
[1411.84 --> 1414.88] And with Vim, there's like a good plugin, which kind of works. |
[1415.30 --> 1418.26] I can share it in the show notes, but it's good. |
[1418.26 --> 1420.66] I mean, it's much better than not having it. |
[1421.12 --> 1423.02] I'm sure that that can improve as well. |
[1423.22 --> 1427.78] There's some rumblings in the queue community around creating a language server as well. |
[1428.06 --> 1429.34] Ooh, wow. |
[1429.36 --> 1429.60] Yes. |
[1429.60 --> 1430.08] An LSP. |
[1430.26 --> 1431.04] I would love that. |
[1431.42 --> 1432.36] I would love that. |
[1432.48 --> 1432.64] Okay. |
[1432.80 --> 1433.08] Okay. |
[1433.16 --> 1433.38] Right. |
[1433.46 --> 1435.50] So, yeah, I'll definitely want to watch for sure. |
[1435.74 --> 1438.30] So what comes next? |
[1438.30 --> 1449.02] I think one thing that occurs to me is, at least as far as I remember, this is currently still using the Docker build. |
[1449.02 --> 1460.16] So you're actually pushing out the contents of a bunch of those steps to the Docker engine to actually then build the image. |
[1461.12 --> 1465.52] And with Europa and some of the improvements there, that should not be necessary. |
[1465.52 --> 1477.00] You should be able to just take the output of one of these stages and just add the information that you want on top of it and be off to the races and then be able to push that directly. |
[1477.20 --> 1486.50] Because right now what's happening is a bunch of the context is still having to be pushed from within BuildKit to Docker engine so that it can build the image. |
[1487.26 --> 1490.18] And that will not be necessary. |
[1490.74 --> 1491.14] Interesting. |
[1491.80 --> 1493.18] With some of the new Europa stuff. |
[1493.18 --> 1493.94] Okay. |
[1494.60 --> 1495.34] Sounds great. |
[1496.48 --> 1499.36] Anything to add, Guillaume, to that or something else? |
[1500.20 --> 1500.46] Yeah. |
[1500.64 --> 1507.22] I think that with Europa, as Joel mentioned earlier, the DX will be far better. |
[1507.52 --> 1515.58] Like what we're trying to do at the moment, if the people watch the PR with Europa, it's going to be, it will feel normal. |
[1515.84 --> 1516.00] Yeah. |
[1516.04 --> 1516.76] I think, yeah. |
[1516.80 --> 1517.96] I think that makes a lot of sense. |
[1518.08 --> 1519.74] Europa will make this a lot simpler. |
[1519.74 --> 1519.86] Yeah. |
[1520.08 --> 1524.70] And while we had like to jump through a couple of hoops, it just made it obvious they shouldn't be there. |
[1525.08 --> 1527.98] And so I'm really excited to adapt this to that new way. |
[1528.24 --> 1528.98] That will be great. |
[1529.18 --> 1530.86] And to see what improvements we can get. |
[1530.94 --> 1532.68] Because at the end of the day, that's what you care about, right? |
[1532.82 --> 1534.38] This looks not as good as it could. |
[1534.64 --> 1536.32] I mean, it works, right? |
[1536.36 --> 1537.26] And that's what you care about. |
[1537.32 --> 1537.82] Make it work. |
[1538.40 --> 1539.08] Make it right. |
[1539.42 --> 1540.40] I think that's what's happening now. |
[1540.42 --> 1541.08] We're making it right. |
[1541.12 --> 1542.16] And then we're making it fast. |
[1542.16 --> 1543.62] So I'm very excited about that. |
[1545.26 --> 1545.66] Okay. |
[1545.74 --> 1549.86] Well, I'm going to wish you both a Merry Christmas, even though this is like weeks before Christmas. |
[1550.02 --> 1553.12] But by the time listeners will be listening to this, it'll be Christmas. |
[1553.94 --> 1555.20] And Happy New Year. |
[1555.60 --> 1555.74] Thanks. |
[1556.82 --> 1559.14] It's been a lot of fun to work with you and Guillaume on this. |
[1560.10 --> 1563.50] It's been a nice opportunity to get to know you and get to know Guillaume as well. |
[1564.34 --> 1568.96] Like you mentioned, I live in kind of the Boulder, Denver area and Guillaume lives in France. |
[1569.62 --> 1574.22] And it was a good opportunity to bump into each other more regularly. |
[1574.96 --> 1575.32] Definitely. |
[1575.54 --> 1576.40] Right back at you again. |
[1577.08 --> 1577.80] Same for me. |
[1577.90 --> 1579.74] So I'm glad that this worked the way you did. |
[1579.86 --> 1580.98] I also had a lot of fun. |
[1581.12 --> 1581.70] Thank you very much. |
[1581.90 --> 1582.20] Thank you. |
[1582.58 --> 1583.12] Thank you. |
[1583.12 --> 1596.36] Our second present to you this Christmas is sharing my way of understanding CPU time used by Kubernetes workloads. |
[1597.08 --> 1605.30] Think near real-time flame graphs, as well as being able to compare CPU profiles for the same process at different points in time. |
[1605.74 --> 1611.02] If you're familiar with Brendan Gregg's book, Systems Performance, this goes really well with it. |
[1611.50 --> 1613.10] So why is this a big deal? |
[1613.54 --> 1616.60] And why was it more difficult to do this in the past? |
[1617.10 --> 1619.82] I know just the right person to unwrap this present with. |
[1620.24 --> 1624.08] Let me talk a little bit about why that's interesting, why that's useful. |
[1625.00 --> 1631.70] So profiling has kind of been in the developer toolbox ever since software engineering has existed, |
[1631.70 --> 1637.94] because we always needed to know, like, why is my program executing and how is it executing the way it is? |
[1638.60 --> 1641.24] And so profiling has been around for a very long time. |
[1641.24 --> 1645.76] It's essentially us recording what the program is doing. |
[1645.76 --> 1656.16] And you can literally think of it as we're recording the stack traces that are happening, you know, 100 times per second. |
[1656.16 --> 1662.14] And that has kind of evolved over the years. |
[1662.86 --> 1670.34] And profiling used to be a very expensive operation to do, which is why you only did it when you really needed to. |
[1670.34 --> 1680.44] And so one thing that kind of changed the perspective was when we discovered sampling profiling. |
[1680.44 --> 1686.52] So in the olden days, the way that profiling worked is that we literally recorded everything that was happening in our program. |
[1687.04 --> 1689.18] And naturally, that's really expensive. |
[1689.90 --> 1694.56] And sampling profiles, profiling kind of go a different strategy and say, |
[1694.86 --> 1698.44] actually, we only need something that's statistically significant. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.