From: | AMatveev(at)bitec(dot)ru |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Craig Ringer <craig(at)2ndquadrant(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: One process per session lack of sharing |
Date: | 2016-07-18 09:38:38 |
Message-ID: | 1622360622.20160718123838@bitec.ru |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi
> I admit that it is risky, but I think there are things that could be
> done to limit the risk. I don't believe we can indefinitely continue
> to ignore the potential performance benefits of making a switch like
> this. Breaking a thirty-year old code base irretrievably would be
> sad, but letting it fade into irrelevance because we're not willing to
> make the architecture changes that are needed to remain relevant would
> be sad, too.
I can add, that nowadays it seems
that the paralleling processing is the only way to scale.
They can't wait that CPU Clock Speeds Increased in in the coming
years.
I understand that use of thread has some difficulties.
I can not understand why use of thread can have disadvantages.
Actually I think that parallelling using threads is much easy than
parallelling using processes.
From | Date | Subject | |
---|---|---|---|
Next Message | AMatveev | 2016-07-18 10:04:26 | Re: One process per session lack of sharing |
Previous Message | Andres Freund | 2016-07-18 09:28:34 | Re: Reviewing freeze map code |