graphql-bench VS postgres-json-schema

(from Hasura)

Scaling subscriptions is hard, but we work with our users/customers at scale to make sure settings are tweaked correctly.

We have users running 100k - 1M concurrent users in production for live-event type platforms. It's not completely trivial to benchmark and setup because query patterns, streaming vs live queries etc have an impact, but it works very reliably. No missing events, no problems disconnecting/reconnecting, no need for sticky sessions and so on.

An initial POC benchmark [1] should be a quick affair so if you're trying it out and run into any problems, please hit me up! Email on my bio.

[1]: https://github.com/hasura/graphql-bench

Has anyone come across neat tools for load-testing streaming APIs?

We used https://github.com/hasura/graphql-bench and a set of scripts to monitor runtime characteristics of Hasura and Postgres, and reconciliation to make sure data was received as expected and in-order.

But would love to see if there's other tools that folks have come across!

Just went through the examples -- I thought it was really neat!

Often times I want/need to display data in more than one format. Usually I just take up a bunch of page space by putting multiple charts.

Here's an example showing what I mean from actual project:

https://github.com/hasura/graphql-bench/raw/master/app/hasur...

If there was a solid and comprehensive charting library that could "tween" between the chart formats, only taking up the space of 1 chart, that would be a neat solution!

Have you found certain pairs/combinations of charts that expose hidden relationships when you display them by animating the data points between them?

I've found that this PL/pgSQL implementation also works well when you don't need maximum performance:

https://github.com/gavinwahl/postgres-json-schema

This is awesome -- really excited that Supabase is picking this up with their commitment to open source in general and PG in particular.

Some prior art:

- https://github.com/gavinwahl/postgres-json-schema (mentioned in the repo)

# Based on debian-slim FROM postgres:12 RUN mkdir -p /app RUN apt-get update # pgroonga extension # Does not officially support alpine RUN apt-get install -y wget RUN wget https://packages.groonga.org/debian/groonga-apt-source-latest-buster.deb RUN apt install -y -V ./groonga-apt-source-latest-buster.deb RUN echo "deb http://apt.postgresql.org/pub/repos/apt/ buster-pgdg main" | tee /etc/apt/sources.list.d/pgdg.list RUN wget --quiet -O - https://www.postgresql.org/media/keys/ACCC4CF8.asc | apt-key add - RUN apt-get update RUN apt-get install -y -V postgresql-12-pgdg-pgroonga RUN apt-get install -y -V groonga-tokenizer-mecab RUN apt-get install -y -V groonga-token-filter-stem RUN apt-get install -y git make # postgres-json-schema extension WORKDIR /app RUN git clone --depth 1 https://github.com/gavinwahl/postgres-json-schema.git RUN cd postgres-json-schema && make install # groonga-tokenizer-friso extension # WORKDIR /app # RUN apt-get install -y build-essential automake libtool libgroonga-dev # RUN git clone --depth 1 https://github.com/kenhys/groonga-tokenizer-friso.git # RUN wget -c https://github.com/lionsoul2014/friso/archive/v1.6.4-release.tar.gz -O - | tar -xz # RUN cd friso-1.6.4-release/src && make && make install # RUN cd groonga-tokenizer-friso && ./autogen.sh && ./configure --with-friso=/usr --with-friso-ini=../friso-1.6.4-release/friso.ini && make && make install # pg_jieba extension WORKDIR /app RUN apt-get install -y cmake build-essential postgresql-server-dev-12 RUN git clone --depth 1 https://github.com/jaiminpan/pg_jieba.git WORKDIR /app/pg_jieba RUN git submodule update --init --recursive RUN mkdir build && cd build && cmake -DPostgreSQL_TYPE_INCLUDE_DIR=/usr/include/postgresql/12/server .. && make && make install