Horton

Re: Security lessons from liblzma

Tom Lane <tgl@sss.pgh.pa.us>

View thread
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Jelte Fennema-Nio <postgres@jeltef.nl>
Cc: Daniel Gustafsson <daniel@yesql.se>, Robert Haas <robertmhaas@gmail.com>, Peter Eisentraut <peter@eisentraut.org>, Andres Freund <andres@anarazel.de>, Bruce Momjian <bruce@momjian.us>, PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Date: 2024-04-04T22:34:30Z
Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Introduce a non-recursive JSON parser

Jelte Fennema-Nio <postgres@jeltef.nl> writes:
> Okay turns out even generating them in parallel isn't any faster than
> running that sequentially. I guess it's because of the strong random
> generation being the slow part. Command I used was the following and
> took ~5 seconds on my machine:

> make -C src/test/ssl sslfiles-clean && make -C src/test/ssl sslfiles -j20

Just for comparison's sake, this takes about 2 minutes on mamba's
host.  Now that's certainly museum-grade hardware, but I don't
think it's even the slowest machine in the buildfarm.  On a
Raspberry Pi 4B, it was about 25 seconds.

(I concur with your result that parallelism helps little.)

			regards, tom lane