Gerhard Lazu

As a TLDR, this change meant that we have less moving parts. And when namespace works, and this is something, again, that we need to understand, why did this run take longer? It should take within two minutes. We should be out. A change should be out in production. Half the time is spent in build, and half the time is spent on deploys.

As a TLDR, this change meant that we have less moving parts. And when namespace works, and this is something, again, that we need to understand, why did this run take longer? It should take within two minutes. We should be out. A change should be out in production. Half the time is spent in build, and half the time is spent on deploys.

So when it comes to optimizing something, now we get to choose which side do we optimize. And I think build, test, and publish is fairly fast. The slower part is the actual deployment. So how can we maybe half that? How can we get those changes once they're finished and everything is bundled? How could we get it out quicker?

So when it comes to optimizing something, now we get to choose which side do we optimize. And I think build, test, and publish is fairly fast. The slower part is the actual deployment. So how can we maybe half that? How can we get those changes once they're finished and everything is bundled? How could we get it out quicker?

i love it i think do you have ideas on that well i think the application boot time could be improved right because it takes a while for the app to boot when i say it takes a while it may take 20 30 seconds for it to be healthy all the connections to be established now i'm not sure exactly which parts of those you know would be the easiest one to optimize

i love it i think do you have ideas on that well i think the application boot time could be improved right because it takes a while for the app to boot when i say it takes a while it may take 20 30 seconds for it to be healthy all the connections to be established now i'm not sure exactly which parts of those you know would be the easiest one to optimize

But I think the application going from the deploy starting and the deploy finishing, taking a minute and a half is a bit long. So I'll need to dig deeper. Like, is it when it comes to connecting to the database? Is it just the application itself being healthy? Like which part needs to be optimized? But again, we're talking, this is like a minute and a half.

But I think the application going from the deploy starting and the deploy finishing, taking a minute and a half is a bit long. So I'll need to dig deeper. Like, is it when it comes to connecting to the database? Is it just the application itself being healthy? Like which part needs to be optimized? But again, we're talking, this is like a minute and a half.

We're optimizing a minute and a half just to put this into perspective. And that's why I started with the question, like how fast is fast enough?

We're optimizing a minute and a half just to put this into perspective. And that's why I started with the question, like how fast is fast enough?

No, that's a good one. That's exactly what, you know, we're like trying to hash it out so that we share the understanding that each of us holds. so that we can, you know, talk about like what would, because we talked about this in the past and I really liked Jared's question.

No, that's a good one. That's exactly what, you know, we're like trying to hash it out so that we share the understanding that each of us holds. so that we can, you know, talk about like what would, because we talked about this in the past and I really liked Jared's question.

He was asking, we're talking about like Kaizen Inc and, you know, we're talking about all this change, but are we actually improving? And that's why when I tried to think about this and I was thinking about like, okay, what would the improvement look like? And can we, I mean, we can measure it and we can check, have we delivered on this?

He was asking, we're talking about like Kaizen Inc and, you know, we're talking about all this change, but are we actually improving? And that's why when I tried to think about this and I was thinking about like, okay, what would the improvement look like? And can we, I mean, we can measure it and we can check, have we delivered on this?

And until like the last deploy that went out, I was fairly happy with the time that the duration that these deploys were taking. But based on the one which I have right in front of me, the build going from one minute and a bit to almost three minutes, I think that variability is something that I would like to understand first before optimizing the boot time.

And until like the last deploy that went out, I was fairly happy with the time that the duration that these deploys were taking. But based on the one which I have right in front of me, the build going from one minute and a bit to almost three minutes, I think that variability is something that I would like to understand first before optimizing the boot time.

Well, let's open up namespace. Let's go to instances. We can see the last build, which you can see here, like all the builds. This is inside Dagger, is that right? This is namespace. All this is namespace, by the way. So we're using namespace for the runners. And I would like... This is a third-party service? It is a third-party service, yes. That you just found or someone told you about?

Well, let's open up namespace. Let's go to instances. We can see the last build, which you can see here, like all the builds. This is inside Dagger, is that right? This is namespace. All this is namespace, by the way. So we're using namespace for the runners. And I would like... This is a third-party service? It is a third-party service, yes. That you just found or someone told you about?

Exactly, yes. I am paying attention to various build services and depot.dev. I love it. Namespace.so. Namespace.so, yes. Our trial is almost over. Exactly, yes. Now, how much will it cost us, by the way? Every minute. Three days left on your trial. Three days left on our trial, yes. I'm getting nervous here. So hang on. Per minute, we're paying $0.0015. $0.0015.

Exactly, yes. I am paying attention to various build services and depot.dev. I love it. Namespace.so. Namespace.so, yes. Our trial is almost over. Exactly, yes. Now, how much will it cost us, by the way? Every minute. Three days left on your trial. Three days left on our trial, yes. I'm getting nervous here. So hang on. Per minute, we're paying $0.0015. $0.0015.