Hi Bharath,
> Few things to follow before testing:
> 1. Is the table being dropped/truncated after the test with 0 workers and before running with 1 worker? If not, then
theindex insertion time would increase.[1](for me it is increasing by 10 sec). This is obvious because the 1st time
indexwill be created from bottom up manner(from leaves to root), but for the 2nd time it has to search and insert at
theproper leaves and inner B+Tree nodes.
Yes, it' being truncated before running each and every COPY.
> 2. If possible, can you also run with custom postgresql.conf settings[2] along with default? Just to ensure that
otherbg processes such as checkpointer, autovacuum, bgwriter etc. don't affect our testcase. For instance, with default
postgresql.conffile, it looks like checkpointing[3] is happening frequently, could you please let us know if that
happensat your end?
Yes, have run with default and your custom settings. With default
settings, I can confirm that checkpointing is happening frequently
with the tests I've run here.
> 3. Could you please run the test case 3 times at least? Just to ensure the consistency of the issue.
Yes, have run 4 times. Seems to be a performance hit (whether normal
copy or parallel-1 copy) on the first COPY run on a freshly created
database. After that, results are consistent.
> 4. I ran the tests in a performance test system where no other user processes(except system processes) are running.
Isit possible for you to do the same?
>
> Please capture and share the timing logs with us.
>
Yes, I have ensured the system is as idle as possible prior to testing.
I have attached the test results obtained after building with your
Parallel Copy patch and testing patch applied (HEAD at
733fa9aa51c526582f100aa0d375e0eb9a6bce8b).
Test results show that Parallel COPY with 1 worker is performing
better than normal COPY in the test scenarios run. There is a
performance hit (regardless of COPY type) on the very first COPY run
on a freshly-created database.
I ran the test case 4 times. and also in reverse order, with truncate
run before each COPY (output and logs named xxxx_0_1 run normal COPY
then parallel COPY, and named xxxx_1_0 run parallel COPY and then
normal COPY).
Please refer to attached results.
Regards,
Greg
