| From: | Markus Schaber <schabi(at)logix-tt(dot)com> |
|---|---|
| To: | Arjen van der Meijden <acmmailing(at)tweakers(dot)net>, pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: PostgreSQL scalability on Sun UltraSparc T1 |
| Date: | 2006-08-07 13:18:27 |
| Message-ID: | 44D73DA3.7080701@logix-tt.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Hi, Arjen,
Arjen van der Meijden wrote:
> It was the 8core version with 16GB memory... but actually that's just
> overkill, the active portions of the database easily fits in 8GB and a
> test on another machine with just 2GB didn't even show that much
> improvements when going to 7GB (6x1G, 2x 512M), it was mostly in the
> range of 10% improvement or less.
I'd be interested in the commit_siblings and commit_delay settings,
tuning them could give a high increase on throughput for highly
concurrent insert/update workloads, at the cost of latency (and thus
worse results for low concurrency situations).
Different fsync method settings can also make a difference (I presume
that syncing was enabled).
HTH,
Markus
--
Markus Schaber | Logical Tracking&Tracing International AG
Dipl. Inf. | Software Development GIS
Fight against software patents in EU! www.ffii.org www.nosoftwarepatents.org
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Markus Schaber | 2006-08-07 13:32:39 | Re: sub select performance due to seq scans |
| Previous Message | Tom Lane | 2006-08-07 12:52:17 | Re: High Context-Switches on Linux 8.1.4 Server |