| From: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
|---|---|
| To: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
| Cc: | Andres Freund <andres(at)2ndquadrant(dot)com>, Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: StrategyGetBuffer optimization, take 2 |
| Date: | 2013-08-15 04:37:46 |
| Message-ID: | CAA4eK1LCTRyCjpOwE3JvaUGSS_0OJ=cnVPmdRwiiGwoR1BPumA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Aug 14, 2013 at 7:00 PM, Merlin Moncure <mmoncure(at)gmail(dot)com> wrote:
> Performance testing this patch is a real bugaboo for me; the VMs I have to
> work with are too unstable to give useful results :-(. Need to scrounge up
> a doner box somewhere...
While doing performance tests in this area, I always had a feeling
that OS layer (scheduler that flushes OS buffers)
had a role to play here, So I use to reboot m/c between tests,
ofcourse taking performance data in this fashion is tedious.
I think it is good to run tests on m/c with configuration similar
to what Jim Nasby mentioned in his below mail.
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2013-08-15 06:20:58 | Re: danger of stats_temp_directory = /dev/shm |
| Previous Message | Peter Eisentraut | 2013-08-15 03:35:45 | Re: updatable/deletable terminology |