Re: COPY performance on Windows

From: Vladlen Popolitov <v(dot)popolitov(at)postgrespro(dot)ru>
To: "Ryohei Takahashi (Fujitsu)" <r(dot)takahashi_2(at)fujitsu(dot)com>
Cc: 'Robert Haas' <robertmhaas(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: COPY performance on Windows
Date: 2024-12-17 11:33:42
Message-ID: 6a9fb94d29a8cc336bcbf5f5c01874c6@postgrespro.ru
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Ryohei Takahashi (Fujitsu) писал(а) 2024-12-16 15:10:

Hi
> According to your advice, I created RAM disk and put input files and
> data directory on RAM disk.
> But the result changed only a few seconds.
> In this test case, the table is unlogged table and shared_buffers is
> enough.
> So, I think the disk performance does not affect so much.
If test on RAM drive got the same result, it could mean, that other
operations affect performance (not disk).
It is only idea, that numeric conversion gives some increase in time due
to new functionality added.
I think, it could be checked, if table has text fields instead of
numeric - we could exclude numeric conversion
and have the same input-output operations (really more IO-operation, but
we need to compare)

> Please use the "test.sh" in the following e-mail.
> https://www.postgresql.org/message-id/flat/TY3PR01MB11891C0FD066F069B113A2376823E2%40TY3PR01MB11891.jpnprd01.prod.outlook.com#8455c9f7b66780a356511f5cfe029d57
OK, I will use it.

By the way, do you use prebuild Postgres versions for this test or
build it by yourself with the same options? I am going to use built
myself.

--
Best regards,

Vladlen Popolitov.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robins Tharakan 2024-12-17 11:50:43 Re: Cutting support for OpenSSL 1.0.1 and 1.0.2 in 17~?
Previous Message Amit Kapila 2024-12-17 11:25:07 Re: Skip collecting decoded changes of already-aborted transactions