From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
---|---|
To: | Ranier Vilela <ranier(dot)vf(at)gmail(dot)com> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: calling procedures is slow and consumes extra much memory against calling function |
Date: | 2020-05-16 03:06:34 |
Message-ID: | CAFj8pRABiMH9zZuqYh13W5g1FYfpcd5vmQsLkNYLE3ys-84Ssw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
so 16. 5. 2020 v 0:34 odesílatel Ranier Vilela <ranier(dot)vf(at)gmail(dot)com> napsal:
> Em dom., 10 de mai. de 2020 às 17:21, Pavel Stehule <
> pavel(dot)stehule(at)gmail(dot)com> escreveu:
>
>> Hi
>>
>> I try to use procedures in Orafce package, and I did some easy
>> performance tests. I found some hard problems:
>>
>> 1. test case
>>
>> create or replace procedure p1(inout r int, inout v int) as $$
>> begin v := random() * r; end
>> $$ language plpgsql;
>>
>> This command requires
>>
>> do $$
>> declare r int default 100; x int;
>> begin
>> for i in 1..300000 loop
>> call p1(r, x);
>> end loop;
>> end;
>> $$;
>>
>> about 2.2GB RAM and 10 sec.
>>
> I am having a consistent result of 3 secs, with a modified version
> (exec_stmt_call) of your patch.
> But my notebook is (Core 5, 8GB and SSD), could it be a difference in the
> testing hardware?
>
My notebook is old T520, and more I have a configured Postgres with
--enable-cassert option.
regards
Pavel
> regards,
> Ranier Vilela
>
From | Date | Subject | |
---|---|---|---|
Next Message | Thomas Munro | 2020-05-16 03:51:41 | Re: pgindent && weirdness |
Previous Message | Michael Paquier | 2020-05-16 01:56:21 | Re: Potentially misleading name of libpq pass phrase hook |