Re: Increase OpenBSD CI task's RAM disk size

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: Nazir Bilal Yavuz <byavuz81(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Andres Freund <andres(at)anarazel(dot)de>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
Subject: Re: Increase OpenBSD CI task's RAM disk size
Date: 2025-09-02 08:24:34
Message-ID: E00AEEE8-A114-47D2-AC0C-B409F8991305@yesql.se
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On 15 Aug 2025, at 12:20, Nazir Bilal Yavuz <byavuz81(at)gmail(dot)com> wrote:
> On Fri, 15 Aug 2025 at 12:19, Daniel Gustafsson <daniel(at)yesql(dot)se> wrote:
>>
>>> On 15 Aug 2025, at 10:46, Nazir Bilal Yavuz <byavuz81(at)gmail(dot)com> wrote:

>>> Sometimes OpenBSD CI tasks fail with 'No space left on device' [1].
>>> It's due to the OpenBSD CI task's RAM disk size being ~3.8 GB. This
>>> patch increases it to ~4.6 GB. I chose this size manually, we can
>>> increase it more.
>>
>> I don't know Cirrus enough to know if this is a daft question, but does this
>> impact the cost (in actual money or credits) for running the CI tests?
>
> I don't expect this to increase costs, and it might even reduce them
> slightly. Disks generally perform slower when free space is low, so
> the change could make OpenBSD CI tasks faster.

Thanks for clarifying, this definitely seems like something we should do to
keep tests from failing.

--
Daniel Gustafsson

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Chao Li 2025-09-02 08:42:24 Fix pg_waldump to exit cleanly at end of WAL
Previous Message Amit Kapila 2025-09-02 07:42:49 Re: Fix use of variable after pfree