mgartner

5 ms·

1.
by mgartner 5y ago
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 wager almost all services besides prototypes that get no use
2.
by mgartner 7y ago
Cool stuff! I've linked to your blog in the pg_flame README.
3.
by mgartner 7y ago
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 virtually instantly, while comparing a bunch of actual time numb
4.
by mgartner 7y ago
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 explanation.
5.
by mgartner 7y ago
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.
6.
by mgartner 7y ago
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 README breaks it up into multiple steps, but maybe I could make
7.
Show HN: pg_flame – flamegraph visualizations of PostgreSQL query plans(github.com)
321 points by mgartner 7y ago|42 comments
8.
by mgartner 7y ago
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.
9.
Truncate vs. Delete: Efficiently Clearing Data from a Postgres Table(lob.com)
20 points by mgartner 7y ago|4 comments
10.
by mgartner 7y ago
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 Javascript, Litmus is similar, albeit not as feature-rich yet.
11.
Show HN: Litmus – Data Validation in Elixir(github.com)
1 points by mgartner 7y ago|1 comments
12.
by mgartner 7y ago
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 health. Heroku's pg-extras inspired this tool. pg_insig
13.
Show HN: Pg_insights – Convenient SQL for monitoring Postgres database health(github.com)
7 points by mgartner 7y ago|1 comments
14.
by mgartner 8y ago
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 default doesn't necessary mean t
15.
by mgartner 8y ago
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/mgartner/node-keep-alive-benchmark
16.
Stop Wasting Connections, Use HTTP Keep-Alive(lob.com)
215 points by mgartner 8y ago|110 comments
17.
by mgartner 11y ago
The overhead of shell calls in Node was a big reason why we avoided trying to patch ImageMagick or other command line program.