MIME-Version: 1.0
References: <3ydjipcr7kbss57nvi67noplncqhesl5eyb6wgol4ccjxynspv@yatlykpribmm>
 <DIM49A100EY1.2YFS2A6WAI3ZJ@jeltef.nl>
 <CAN55FZ30Np67cATsqYxF1SsP598VoRv4hJQZ4w9RA3Qe55prnQ@mail.gmail.com>
 <CAN55FZ13uX0cLSbgtSnnFeh5sTLeMr7+8UzmqpU6QjOtrRJTLg@mail.gmail.com>
 <qe4lh2i5di2gh7bxkbfisifaohrvyfukbybwxwzxdnll45hnt3@luod7i2mon67>
 <CAN55FZ1-qiOWtQH5o6Q_7LJ7S3Ef_hfDE068uP0hGjB3gzwghg@mail.gmail.com>
 <CAOYmi+kB4Tv8-iVvJK=+8xrPdKZ=bq==gXR2rOHr1wM8TVzPnw@mail.gmail.com>
 <CAN55FZ2kaNRGjV7ai3LN+zASNUf74FsQLa9xoAL6Zb7txLix2A@mail.gmail.com>
In-Reply-To: 
 <CAN55FZ2kaNRGjV7ai3LN+zASNUf74FsQLa9xoAL6Zb7txLix2A@mail.gmail.com>
From: Jakub Wartak <jakub.wartak@enterprisedb.com>
Date: Fri, 29 May 2026 13:38:17 +0200
Message-ID: 
 <CAKZiRmzd_N2cR7OE+k6fQNTAB0zxDFb0J3JPxLUCbf3FzE--pA@mail.gmail.com>
Subject: Re: Heads Up: cirrus-ci is shutting down June 1st
To: Nazir Bilal Yavuz <byavuz81@gmail.com>
Cc: Jacob Champion <jacob.champion@enterprisedb.com>,
 Andres Freund <andres@anarazel.de>,
	Jelte Fennema-Nio <postgres@jeltef.nl>,
 Thomas Munro <thomas.munro@gmail.com>,
	pgsql-hackers@postgresql.org, Zsolt Parragi <zsolt.parragi@percona.com>,
	Peter Eisentraut <peter@eisentraut.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: 
 <https://www.postgresql.org/message-id/CAKZiRmzd_N2cR7OE%2Bk6fQNTAB0zxDFb0J3JPxLUCbf3FzE--pA%40mail.gmail.com>
Precedence: bulk

On Fri, May 29, 2026 at 11:51=E2=80=AFAM Nazir Bilal Yavuz <byavuz81@gmail.=
com> wrote:
[..]
Hi, thanks to everybody for working on this.

> https://github.com/nbyavuz/postgres/actions/runs/26628396798

Windows (runs-on: windows-2022) seems kind of slow isn't it ?

Maybe that's not related to the patch itself, but any idea why the windows
tests are so slow? Or will we able to somehow accelerate those?

Windows - VS - Meson & ninja / succeeded [..] minutes ago in 31m 28s

Processor(s):              1 Processor(s) Installed.
[..]
Total Physical Memory:     16,379 MB
[..]

but:
NUMBER_OF_PROCESSORS=3D4
[..]
+      TEST_JOBS: 8

vs

392/396 test_json_parser - postgresql:test_json_parser/002_inline
                 OK              152.56s   3712 subtests passed
393/396 pgbench - postgresql:pgbench/001_pgbench_with_server
                 OK              574.61s   474 subtests passed
394/396 pg_rewind - postgresql:pg_rewind/002_databases
                 OK              772.86s   10 subtests passed
395/396 pg_waldump - postgresql:pg_waldump/001_basic
                 OK              771.19s   156 subtests passed
396/396 libpq_pipeline - postgresql:libpq_pipeline/001_libpq_pipeline
                 OK              395.76s   23 subtests passed

while last CirrusCI run for me for Windows took 19min 21s (4 CPUs / 4 GBs,
but sysinfo reported there "Total Physical Memory: 16,380 MB").

If that's IO traffic as Andres described, maybe we could enable feature
called "Turn off Windows write-cache buffer flushing on the device"
in device manager -> disk -> policies, but dunno how much that would
help really as we seem to be already using fsync=3Doff, maybe it helps
when saving other files too (???)

-J.