| From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
|---|---|
| To: | Magnus Hagander <magnus(at)hagander(dot)net>, Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-www(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Premature timeout on git.postgresql.org? |
| Date: | 2022-02-20 16:31:23 |
| Message-ID: | 6d164f4c-b89d-5e70-e064-f49c697ba066@aklaver.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-www |
On 2/20/22 07:07, Magnus Hagander wrote:
> On Sun, Feb 20, 2022 at 3:52 PM Bruce Momjian <bruce(at)momjian(dot)us> wrote:
>>
>
> I get about 50MB/500Mbit per second when I clone from it. The git
> server is physically located in Amsterdam, maybe you have a limited
> transit performance there (or it has to you).
>
> Can you, as well, try again now and see if you see the same level of
> performance now?
>
For a point of reference I just cloned on a Linode instance in Fremont
CA. For the Postgres repo I got 2.25 MiB/s. Trying some other project
repos I got 25-27 MiB/s
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2022-02-20 16:54:26 | Re: Premature timeout on git.postgresql.org? |
| Previous Message | Magnus Hagander | 2022-02-20 15:07:49 | Re: Premature timeout on git.postgresql.org? |