Viewing profile — mgartner

It seems like you’re defining “scaling” as growth of a workload to the point that it cannot be handled by a single-server DB. But with any service without a constant workload (I’d …

Cool stuff! I've linked to your blog in the pg_flame README.

I think the text display is great too! I built pg_flame mostly to help understand the relative timing of each step. Your brain can compare the size of each bar in a flamegraph virt…

Ya, I ran into problems with CTE InitPlan steps. However, I did do some extra work to have them display in the most correct way I could think of. I’ll add a CTE demo with and expla…

I built it as a CLI because of the reasons you mention, but also because I find that workflow most convenient for me and I didn’t want to need an internet connection.

If you run the psql client from your dev machine, there’s no need for step 2. Also, in practice I don’t save the output JSON to a file, I just pipe it directly to pg_flame. The REA…

You're totally right. In our case, our test infrastructure spins up a new Postgres container for every build. Because it's not a long-running database, bloat is not a concern.

Litmus is an Elixir library built at Lob for validating user input. We use it to validate API parameters are in the correct form. If you’ve ever used something like Joi in Javascri…

This is an evolving collection of useful SQL for checking in on some important PG metrics. It's been a valuable resource recently at Lob to check in on our Postgres usage and healt…

Based on https://en.wikipedia.org/wiki/HTTP_persistent_connection#HTT... it sounds like your statement is correct. But the fact that the underlying HTTP connection is kept-alive by…

These metrics were collected for HTTPS specifically. I've omitted the URL I used in the benchmark scripts, but am using an HTTPS agent. Scripts live here: https://github.com/mgartn…

The overhead of shell calls in Node was a big reason why we avoided trying to patch ImageMagick or other command line program.