Postgres Pro
Downloads
Home   >   mailing lists

Re: Update on the spinlock->pthread_mutex patch experimental: replace s_lock spinlock code with pthread_mutex on linux - Mailing list pgsql-hackers

From Andres Freund
Subject Re: Update on the spinlock->pthread_mutex patch experimental: replace s_lock spinlock code with pthread_mutex on linux
Date
Msg-id 201206291911.51506.andres@2ndquadrant.com
Whole thread Raw
In response to Update on the spinlock->pthread_mutex patch experimental: replace s_lock spinlock code with pthread_mutex on linux  (Nils Goroll <slink@schokola.de>)
Responses Re: Update on the spinlock->pthread_mutex patch experimental: replace s_lock spinlock code with pthread_mutex on linux  (Nils Goroll <slink@schokola.de>)
Re: Update on the spinlock->pthread_mutex patch experimental: replace s_lock spinlock code with pthread_mutex on linux  (Merlin Moncure <mmoncure@gmail.com>)
List pgsql-hackers
Tree view 
On Friday, June 29, 2012 07:07:11 PM Nils Goroll wrote:
> > Also, 20 transactions per connection is not enough of a run to make
> > any evaluation on.
> 
> As you can see I've repeated the tests 10 times. I've tested slight
> variations as mentioned above, so I was looking for quick results with
> acceptable variation.
Running only 20 transactions is still meaningless. Quite often that will means 
that no backends run concurrently because the starting up takes longer than to 
process those 20 transactions. You need at the very, very least 10s. Check out 
-T.

Andres
-- Andres Freund                       http://www.2ndQuadrant.com/PostgreSQL Development, 24x7 Support, Training &
Services

pgsql-hackers by date:

Previous
From: Josh Berkus
Date:
Subject: Re: Posix Shared Mem patch
Next
From: Nils Goroll
Date:
Subject: Re: Update on the spinlock->pthread_mutex patch experimental: replace s_lock spinlock code with pthread_mutex on linux