text stringlengths 0 2.02k |
|---|
**Gerhard Lazu:** Right. \[laughs\] |
**Jerod Santo:** It's not gonna be distributed, it's just us. \[laughs\] |
**Gerhard Lazu:** Well, it will come from all Fastly endpoints, I imagine... |
**Jerod Santo:** That's true, it could come from lots of different Fastly points of presence... |
**Gerhard Lazu:** Yeah. We could run it elsewhere, I suppose, but I like things being self-contained. I like things being declared in a single place. So to me, it makes most sense to use the same setup. I mean, it is in a way a Fastly limitation, and actually specifically Fastly and Grafana Cloud, the lack of integrati... |
**Jerod Santo:** Right. |
**Gerhard Lazu:** But speaking of that, I know that Honeycomb supports Fastly logging directly... And one of the examples that Honeycomb has is the RubyGems.org traffic, which is also proxied by Fastly. So in their "Try Honeycomb out" you can play with the dataset which is the RubyGems.org traffic. So I know that that ... |
**Jerod Santo:** Just a place to start, yeah. |
**Gerhard Lazu:** Yeah. But then we're using Grafana Cloud for everything else, so... |
**Jerod Santo:** Right. |
**Gerhard Lazu:** ...that's an interesting moment... Like, do we start moving stuff across to Honeycomb, or do we have two systems? |
**Jerod Santo:** Right. That's like a little break in the dam, like a little water just starts to pour out... And it's not a big deal right now, on Grafana Cloud, right? Like, "Well, I've got just this little thing over here on Honeycomb..." |
**Gerhard Lazu:** 99%, yeah. |
**Jerod Santo:** It turns out pretty nice over there... And then it starts to crack a little bit, and more water starts to... And all of a sudden it just bursts, and Grafana loses a customer. That stuff happens. So we could also parallelize this, and we could simultaneously try to get Fastly and Grafana sitting in a tr... |
**Gerhard Lazu:** Yeah, that would be great. That is actually a request from us. |
**Jerod Santo:** And that would probably be in the benefit of both Fastly and Grafana. That would be in both entities -- to their benefit. So maybe it's already in the works, who knows. |
**Adam Stacoviak:** I would guess that it is. |
**Gerhard Lazu:** Well, I would like to know, because then we could be not doing a bunch of work... |
**Jerod Santo:** Then we could procrastinate till it's there... |
**Adam Stacoviak:** Exactly, yeah. |
**Gerhard Lazu:** But it's stuff like this, right? |
**Adam Stacoviak:** Well, let's put an email feeler out. We've got some people we can talk to to know for sure... And then if it is in the works, and it's maybe on the back-burner, we can put some fire under the burner, because we need it, too. |
**Gerhard Lazu:** Well, then we've hit another interesting thing, in that I really wanna try Honeycomb out. I've signed up, and I wanna start sending some events their way and just start using Honeycomb to see what insights we can derive from the things that we do. |
\[47:49\] One of the things that I really wanna track with Honeycomb - and I wasn't expecting to discuss this, but it seems to be related, so why not... I wanna visualize how long it takes from git push to deploy. Because there are many things that happen in that pipeline, and from the past episodes, this is really imp... |
So we don't really know, first of all -- I mean, in my head I know what they are, all the steps, but you and Jerod don't know. What does the git push have to go through before it goes out into prod, and what are all the things that may go wrong? And then which is the area or which is the step which takes the longest am... |
Charity Majors - I don't know which episode, but she will be on the show very soon. 15 minutes or bust. That's what it means. Your code is either in production in 15 minutes, or you're bust. |
**Jerod Santo:** There was an unpopular opinion shared on Go Time. I can't remember who shared it, but he said if it's longer than 10 minutes, you're bust. |
**Gerhard Lazu:** There you go. |
**Jerod Santo:** So that 15 minutes is gonna be moving, I think... |
**Gerhard Lazu:** It will be moving, exactly. |
**Jerod Santo:** As the industry pushes forward, it's gonna keep going lower and lower, right? |
**Gerhard Lazu:** Exactly. |
**Adam Stacoviak:** Well, what is it that -- does every git push, which is from local to presumably GitHub in our case (it could be another code host), is there a way to scrutinize, like "Oh, this is just views and CSS changing to make that deployment faster"? You know, like it was not involving images or a bunch of ot... |
**Gerhard Lazu:** You're right. So the steps that we go through - they're always the same. We could make the pipeline smarter, in that for example if the code doesn't change, you don't need to run the tests. The tests themselves, they don't take long to run. But to run the tests, you need to get the dependencies. And w... |
**Jerod Santo:** You effectively introduce a big cache invalidation problem. |
**Gerhard Lazu:** Yes. |
**Jerod Santo:** \[51:41\] It's what you do. Cache invalidation is one of the hard things in computer science. So it's slow, but it's simple. It's like, "We'll just rebuild it every time." It's like, why does React re-render the entire DOM every time? Well, it doesn't anymore, because that was too slow, so it does all ... |
**Gerhard Lazu:** Yeah. |
**Jerod Santo:** What I'm saying - there's small things you can do. You can get the 80% thing, and it works mostly; it doesn't squeeze out every performance, but it's a big -- so there's probably some low-hanging fruit we could do... But it's surprisingly complicated to do that kind of stuff. |
**Gerhard Lazu:** And the first step really is trying to understand, these 15 minutes, first of all, how much they vary... Because as it says, sometimes they can take 20 minutes. Why does it vary by that much? Maybe, for example, it's test jobs being queued up in CircleCI. A lot of the time that happens, and they are q... |
**Jerod Santo:** Yeah, that's why I said there's probably some low-hanging fruit, and we could probably do a little bit of recon and knock that down quite a bit. |
**Gerhard Lazu:** And that's exactly why I'm thinking, use Honeycomb just to try and visualize those steps, what they are, how they work, and stuff like that... |
**Jerod Santo:** Yeah, see the workflow. |
**Gerhard Lazu:** Exactly. |
**Jerod Santo:** Good idea. |
**Gerhard Lazu:** Second thing is -- and I think this can either be a managed PostgreSQL database, so that either CockroachDB or anyone that manages PostgreSQL, like one of our partners, one of our sponsors, I would like us to offload that problem... And we just get the metrics out of it, understand how well it behaves... |
**Adam Stacoviak:** I remember slacking "How can our Postgres be out of memory?" It's like... wasn't it with the backup? The backup got... something happened with the backup... |
**Jerod Santo:** The WAL files.. the cache got full. |
**Gerhard Lazu:** Yeah, the replication got stuck, and it was broken, it just wouldn't resume, and the disk would fill up crazy. Crazy, crazy. |
**Adam Stacoviak:** And that's the reason you would wanna use a managed because they handle a lot of that stuff for you. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.