| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | pgsql-performance(at)postgresql(dot)org |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Manfred Spraul <manfred(at)colorfullife(dot)com>, neilc(at)samurai(dot)com, markw(at)osdl(dot)org |
| Subject: | Re: futex results with dbt-3 |
| Date: | 2004-10-19 21:59:48 |
| Message-ID: | 200410191459.48080.josh@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Tom,
> The bigger problem here is that the SMP locking bottlenecks we are
> currently seeing are *hardware* issues (AFAICT anyway). The only way
> that futexes can offer a performance win is if they have a smarter way
> of executing the basic atomic-test-and-set sequence than we do;
> and if so, we could read their code and adopt that method without having
> to buy into any large reorganization of our code.
Well, initial results from Gavin/Neil's patch seem to indicate that, while
futexes do not cure the CSStorm bug, they do lessen its effects in terms of
real performance loss.
--
--Josh
Josh Berkus
Aglio Database Solutions
San Francisco
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Barnard | 2004-10-19 22:09:21 | Re: [PERFORM] Performance on Win32 vs Cygwin |
| Previous Message | Tom Lane | 2004-10-19 21:52:13 | Re: futex results with dbt-3 |