Re: Let's make PostgreSQL multi-threaded - Mailing list pgsql-hackers

From Pavel Borisov
Subject Re: Let's make PostgreSQL multi-threaded
Date
Msg-id CALT9ZEH_ZT6Fv8KFmEPf2qM7g0Y0mdU-J4PQDVRN+vhn0CLSOQ@mail.gmail.com
Whole thread Raw
In response to Re: Let's make PostgreSQL multi-threaded  (Dilip Kumar <dilipbalaut@gmail.com>)
Responses Re: Let's make PostgreSQL multi-threaded
Re: Let's make PostgreSQL multi-threaded
List pgsql-hackers
Is the following true or not?

1. If we switch processes to threads but leave the amount of session
local variables unchanged, there would be hardly any performance gain.
2. If we move some backend's local variables into shared memory then
the performance gain would be very near to what we get with threads
having equal amount of session-local variables.

In other words, the overall goal in principle is to gain from less
memory copying wherever it doesn't add the burden of locks for
concurrent variables access?

Regards,
Pavel Borisov,
Supabase



pgsql-hackers by date:

Previous
From: "Joel Jacobson"
Date:
Subject: Re: Let's make PostgreSQL multi-threaded
Next
From: Yuya Watari
Date:
Subject: Re: Making empty Bitmapsets always be NULL