| From: | David Raymond <David(dot)Raymond(at)tomtom(dot)com> |
|---|---|
| To: | Daniele Varrazzo <daniele(dot)varrazzo(at)gmail(dot)com> |
| Cc: | "psycopg(at)postgresql(dot)org" <psycopg(at)postgresql(dot)org> |
| Subject: | RE: CPU usage for queries, psycopg 2 vs 3 |
| Date: | 2023-09-20 14:27:27 |
| Message-ID: | DB7PR07MB391650DB3D30B796DE2F81F687F9A@DB7PR07MB3916.eurprd07.prod.outlook.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | psycopg |
Looks good. With the change it quietly idles while waiting for query results, with no CPU spike.
-David
> Hello David,
>
> On Thu, 7 Sept 2023 at 14:17, David Raymond <David(dot)Raymond(at)tomtom(dot)com> wrote:
>>
>> > Could you please be so kind as to repeat your tests with psycopg 3.1.4?
>> Tried with 3.1.4 and it has idle processor usage while waiting for the 8 results, just like psycopg2.
>> Tried with 3.1.5 and it spikes up to 62% reported CPU usage while waiting for the 8 results, just like the current release.
> I am not able to quickly investigate this issue, because I don't have
> a Windows machine handy. However I would like to release 3.1.11 soon,
> so I would like to merge this changeset, which should revert the wait
> function to what was in 3.1.4 on Windows:
> Are you able to test it to verify that CPU usage is regular with this changeset?
> Cheers
> -- Daniele
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Daniele Varrazzo | 2023-09-21 09:28:28 | Re: CPU usage for queries, psycopg 2 vs 3 |
| Previous Message | Daniele Varrazzo | 2023-09-19 20:44:20 | Re: CPU usage for queries, psycopg 2 vs 3 |