Re: FP16 Support?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Kohei KaiGai <kaigai(at)heterodb(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: FP16 Support?
Date: 2017-11-14 01:21:47
Message-ID: 11483.1510622507@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Kohei KaiGai <kaigai(at)heterodb(dot)com> writes:
> How about your thought for support of half-precision floating point,
> FP16 in short?

This sounds like a whole lotta work for little if any gain. There's not
going to be any useful performance gain from using half-width floats
except in an environment where it's the individual FLOPs that dominate
your costs. PG is not designed for that sort of high-throughput
number-crunching, and it's not likely to get there anytime soon.

When we can show real workloads where float32 ops are actually the
dominant time sink, it would be appropriate to think about whether
float16 is a useful solution. I don't deny that we could get there
someday, but I think putting in float16 now would be a fine example
of having your priorities reversed.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2017-11-14 01:32:30 Re: FP16 Support?
Previous Message Masahiko Sawada 2017-11-14 01:07:09 Re: [HACKERS] ginInsertCleanup called from vacuum could still miss tuples to be deleted