| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Justin Pryzby <pryzby(at)telsasoft(dot)com> |
| Cc: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org, Andrew Dunstan <andrew(at)dunslane(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Subject: | Re: Cygwin cleanup |
| Date: | 2022-08-04 04:06:05 |
| Message-ID: | 20220804040605.izlmfu6wxmuhl7np@awork3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
On 2022-07-28 17:23:19 -0500, Justin Pryzby wrote:
> On Fri, Jul 29, 2022 at 10:04:04AM +1200, Thomas Munro wrote:
> > > > XXX This should use a canned Docker image with all the right packages
> > > > installed
> > >
> > > Has anyone tried using non-canned images ? It sounds like this could reduce
> > > the 4min startup time for windows.
> > >
> > > https://cirrus-ci.org/guide/docker-builder-vm/#dockerfile-as-a-ci-environment
> >
> > Yeah, I had that working once. Not sure what the pros and cons would be for us.
>
> I think it could be a lot faster to start, since cirrus caches the generated
> docker image locally. Rather than (I gather) pulling the image every time.
I'm quite certain that is not true. All the docker images built are just
uploaded to the google container registry and then downloaded onto a
*separate* windows host. The dockerfile: stuff generates a separate task
running on a separate machine...
It's a bit better for non-windows containers, because there google has some
optimization for pulling image (pieces) on demand or such.
Greetings,
Andres Freund
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2022-08-04 04:09:19 | Re: Cleaning up historical portability baggage |
| Previous Message | Amit Kapila | 2022-08-04 04:05:32 | Re: [PATCH] Use indexes on the subscriber when REPLICA IDENTITY is full on the publisher |