Re: Spinlock backoff algorithm - Mailing list pgsql-hackers

From Zdenek Kotala
Subject Re: Spinlock backoff algorithm
Date
Msg-id 47416C91.8080201@sun.com
Whole thread Raw
In response to Re: Spinlock backoff algorithm  (Gregory Stark <stark@enterprisedb.com>)
List pgsql-hackers
Gregory Stark wrote:
> "Tom Lane" <tgl@sss.pgh.pa.us> writes:
> 
>> Mark Mielke <mark@mark.mielke.cc> writes:
>>> Tom Lane wrote:
>>>> My goodness that's a hardware-dependent proposal.  Shall we discuss
>>>> how many CPUs there are where an integer division is *slower* than
>>>> a floating-point op?
>>> Do you have one in mind, or is this a straw man? :-)
>> I've got one upstairs (HPPA), and I believe that it's actually a pretty
>> common situation in scientifically-oriented workstations from a few
>> years back.
> 
> I think floating point is fast on many common platforms, even many i386
> variants. But usually that's assuming you're comparing doing a whole bunch of
> work in floating point or integer math. Converting a bunch of integers to
> floating point for a single operation doesn't seem like a case that's going to
> shine on any floating point unit.

Just for fullness, task context switch is more complex (slower) when 
application uses FP operation. It is not important for PostgreSQL 
because it has FP operation on many places, but it is good to know.

    Zdenek



pgsql-hackers by date:

Previous
From: Kris Jurka
Date:
Subject: Re: pgsql: New versions of mingw have gettimeofday(), so add an autoconf
Next
From: Alvaro Herrera
Date:
Subject: Re: VACUUM/ANALYZE counting of in-doubt tuples