Menu
Sign In Search Podcasts Charts People & Topics Add Podcast API Blog Pricing

Gerhard Lazu

๐Ÿ‘ค Speaker
1554 total appearances

Appearances Over Time

Podcast Appearances

So I appreciate it. It gives us another dimension. It's playful. It's, you know, like there is some fun to be had here. It's not just all serious. It's not like another news channel, but it's really, really nice. Like the whole thing, it feels so much more polished compared to last time. I can definitely see like the tiny, tiny improvements. Yeah. Very cool. So much Kaizen. Indeed. Cool.

So I appreciate it. It gives us another dimension. It's playful. It's, you know, like there is some fun to be had here. It's not just all serious. It's not like another news channel, but it's really, really nice. Like the whole thing, it feels so much more polished compared to last time. I can definitely see like the tiny, tiny improvements. Yeah. Very cool. So much Kaizen. Indeed. Cool.

Well, the next big item on my list is to talk about twice, 2x faster time to deploy. This is something we just spent a bit of time on. I was surprised, by the way, of the latest deploy. It was slower than 2x, but we can get there. Okay. The first thing which I would like to ask is how do you feel about our application deploys in general? Like, Does it feel slow? Does it feel fast?

Well, the next big item on my list is to talk about twice, 2x faster time to deploy. This is something we just spent a bit of time on. I was surprised, by the way, of the latest deploy. It was slower than 2x, but we can get there. Okay. The first thing which I would like to ask is how do you feel about our application deploys in general? Like, Does it feel slow? Does it feel fast?

Does it feel okay? Do you feel surprised by something? How do application deploys when you push a change to a repo feel to you? Historically or after this change?

Does it feel okay? Do you feel surprised by something? How do application deploys when you push a change to a repo feel to you? Historically or after this change?

Okay, okay. So what would make them not too slow? Is there like a duration? Maybe like a 2x. 2x, okay. That's so leading though. I literally meant like how many minutes or seconds, I think we talked about that. Would it feel that it's good enough?

Okay, okay. So what would make them not too slow? Is there like a duration? Maybe like a 2x. 2x, okay. That's so leading though. I literally meant like how many minutes or seconds, I think we talked about that. Would it feel that it's good enough?

Okay. That's a good one. So what used to happen before this change, we used to run a dagger engine on the fly so that it would cache previous operations. Okay. so that subsequent runs will be much quicker, especially when nothing changes or very little changes.

Okay. That's a good one. So what used to happen before this change, we used to run a dagger engine on the fly so that it would cache previous operations. Okay. so that subsequent runs will be much quicker, especially when nothing changes or very little changes.

The problem with that approach was that from GitHub Actions, you had to open a WireGuard tunnel into FLY so that you'd have that connectivity to the engine. And what would happen quite often is that tunnel, for whatever reason, would maybe be established, but you couldn't connect to the instance correctly, and you would only find that out a minute or two within the run.

The problem with that approach was that from GitHub Actions, you had to open a WireGuard tunnel into FLY so that you'd have that connectivity to the engine. And what would happen quite often is that tunnel, for whatever reason, would maybe be established, but you couldn't connect to the instance correctly, and you would only find that out a minute or two within the run.

And then what used to happen, you would fall back to GitHub, which is much slower because there's no caching, there's no previous state, and the runners themselves, because they're free, they are slower. Two CPUs and seven gig, which means that you have to, when you have to recompile the application from scratch, it can easily take seven, eight, 10 minutes.

And then what used to happen, you would fall back to GitHub, which is much slower because there's no caching, there's no previous state, and the runners themselves, because they're free, they are slower. Two CPUs and seven gig, which means that you have to, when you have to recompile the application from scratch, it can easily take seven, eight, 10 minutes.

And that's what would lead to those really slow deploys. So what we did between the Kaizens, since the last Kaizen, Let me see which pull request was that. It was pull request 522. So you can go and check it out to see what that looks like.

And that's what would lead to those really slow deploys. So what we did between the Kaizens, since the last Kaizen, Let me see which pull request was that. It was pull request 522. So you can go and check it out to see what that looks like.