Quick Links

Re: Benchmarking: How to identify bottleneck (limiting factor) and achieve "linear scalability"?

From:	Saurabh Nanda <saurabhnanda(at)gmail(dot)com>
To:	Jeff Janes <jeff(dot)janes(at)gmail(dot)com>
Cc:	pgsql-performance(at)lists(dot)postgresql(dot)org
Subject:	Re: Benchmarking: How to identify bottleneck (limiting factor) and achieve "linear scalability"?
Date:	2019-01-28 05:03:21
Message-ID:	CAPz=2oEgTA3ENcUGEFQKGug09gWDw7ixrOLXpK3FenTiPVcXxQ@mail.gmail.com
Views:	Raw Message \| Whole Thread \| Download mbox \| Resend email
Thread:
Lists:	pgsql-performance

All this benchmarking has led me to a philosophical question, why does PG
need shared_buffers in the first place? What's wrong with letting the OS do
the caching/buffering? Isn't it optimised for this kind of stuff?

In response to

Re: Benchmarking: How to identify bottleneck (limiting factor) and achieve "linear scalability"? at 2019-01-28 04:59:41 from Saurabh Nanda

Responses

Re: Benchmarking: How to identify bottleneck (limiting factor) and achieve "linear scalability"? at 2019-01-28 14:03:31 from Saurabh Nanda
Re: Benchmarking: How to identify bottleneck (limiting factor) and achieve "linear scalability"? at 2019-01-29 15:42:12 from Jeff Janes

Browse pgsql-performance by date

	From	Date	Subject
Next Message	Mariel Cherkassky	2019-01-28 10:04:37	upgrade from 9.6 to 10/11
Previous Message	Saurabh Nanda	2019-01-28 04:59:41	Re: Benchmarking: How to identify bottleneck (limiting factor) and achieve "linear scalability"?