Gerhard Lazu

So what we see here in the Neon console, we see our main database. we can see that we have been using 0.04% of a CPU. So really not CPU, but in terms of memory, we have eight allocated. We're using 1.3 gigabytes. 1.3 gigabytes used out of eight allocated. So we are over-allocating both CPU and memory. So fairly little load, I would say, and things are just humming along. So no issues whatsoever.

So what we see here in the Neon console, we see our main database. we can see that we have been using 0.04% of a CPU. So really not CPU, but in terms of memory, we have eight allocated. We're using 1.3 gigabytes. 1.3 gigabytes used out of eight allocated. So we are over-allocating both CPU and memory. So fairly little load, I would say, and things are just humming along. So no issues whatsoever.

Yes, I was. I didn't get to that, but that would not use this database, by the way. That would be something different now.

Yes, I was. I didn't get to that, but that would not use this database, by the way. That would be something different now.

Right. I would, but not in this production database. So this is special, right? I mean, this is exactly what we want to see. If anything, we can, because we have the minimum compute setting set to two CPUs and eight gigs of memory. And I know that Neon does an excellent job of auto-scaling us when we need to. We didn't need to get auto-scaled because we are below the minimum threshold.

Right. I would, but not in this production database. So this is special, right? I mean, this is exactly what we want to see. If anything, we can, because we have the minimum compute setting set to two CPUs and eight gigs of memory. And I know that Neon does an excellent job of auto-scaling us when we need to. We didn't need to get auto-scaled because we are below the minimum threshold.

So we could maybe even lower the threshold and it would still be fine.

So we could maybe even lower the threshold and it would still be fine.

So we need some arbitrary workloads in order to push it. Well, to see where it breaks, we wouldn't need it to break. I think if anything, one thing that I would like us to do more is use Neon for development databases. And I have something there I haven't finished, but I would like to move on to that as well, if everyone's fine.

So we need some arbitrary workloads in order to push it. Well, to see where it breaks, we wouldn't need it to break. I think if anything, one thing that I would like us to do more is use Neon for development databases. And I have something there I haven't finished, but I would like to move on to that as well, if everyone's fine.

Yes, that's coming. That's my next topic to share. What exactly is that? Well, that would mean tooling that's local to make all of this easy. Jared wouldn't need to go to the UI to click any buttons to do anything. He would just run a command locally and the thing would happen locally. He wouldn't need to even open this UI. Shouldn't that be a Neon native thing though? It is.

Yes, that's coming. That's my next topic to share. What exactly is that? Well, that would mean tooling that's local to make all of this easy. Jared wouldn't need to go to the UI to click any buttons to do anything. He would just run a command locally and the thing would happen locally. He wouldn't need to even open this UI. Shouldn't that be a Neon native thing though? It is.

It does have a CLI, but the problem is you need to, first of all, install the CLI, configure the CLI, like add quite a few flags, connect the CLI to your local Postgres, like all that glue. That's the stuff which I've been working on. And I can talk about that a bit more.

It does have a CLI, but the problem is you need to, first of all, install the CLI, configure the CLI, like add quite a few flags, connect the CLI to your local Postgres, like all that glue. That's the stuff which I've been working on. And I can talk about that a bit more.

Some command that you run locally that knows what the sequence of the steps is and what to do. For example, maybe you don't have the CLI installed. Well, install the CLI. you need to have some secrets. Well, here's the one password CLI. And by the way, the secrets is here, like in this vault. So stuff like that, like all that. Yeah.

Some command that you run locally that knows what the sequence of the steps is and what to do. For example, maybe you don't have the CLI installed. Well, install the CLI. you need to have some secrets. Well, here's the one password CLI. And by the way, the secrets is here, like in this vault. So stuff like that, like all that. Yeah.

So it's possible to use something else. But at the end of the day, it's like the integration needs to work. And the implementation, whether you use the SDK or whether you use the CLI, is just an implementation. Just doesn't matter, yeah. What we care about is like, is it reliable, our implementation? Do we have any issues with it? So far, no. Yeah. Are we using like service accounts?

So it's possible to use something else. But at the end of the day, it's like the integration needs to work. And the implementation, whether you use the SDK or whether you use the CLI, is just an implementation. Just doesn't matter, yeah. What we care about is like, is it reliable, our implementation? Do we have any issues with it? So far, no. Yeah. Are we using like service accounts?

And that's something that we've been waiting because without service accounts, you would need to set up a connect server, which I didn't want to do. So that was a big deal for us. Whether you use the CLI or the SDK, we could, but it wouldn't make that much of a difference. Now, if the application itself, while it runs, it was doing certain things,

And that's something that we've been waiting because without service accounts, you would need to set up a connect server, which I didn't want to do. So that was a big deal for us. Whether you use the CLI or the SDK, we could, but it wouldn't make that much of a difference. Now, if the application itself, while it runs, it was doing certain things,