From: | Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk> |
---|---|
To: | Andres Freund <andres(at)anarazel(dot)de> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Alexander Kuzmenkov <a(dot)kuzmenkov(at)postgrespro(dot)ru>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | Re: Performance improvements for src/port/snprintf.c |
Date: | 2018-09-27 03:53:27 |
Message-ID: | 87r2hffwda.fsf@news-spur.riddles.org.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
>>>>> "Andres" == Andres Freund <andres(at)anarazel(dot)de> writes:
Andres> Hm, stb's results just for floating point isn't bad. The above
Andres> numbers were for %f %f. But as the minimal usage would be about
Andres> the internal usage of dopr(), here's comparing %.*f:
Andres> snprintf time = 1324.87 ms total, 0.000264975 ms per iteration
Andres> pg time = 1434.57 ms total, 0.000286915 ms per iteration
Andres> stbsp time = 552.14 ms total, 0.000110428 ms per iteration
Hmm. We had a case recently on IRC where the performance of float8out
turned out to be the major bottleneck: a table of about 2.7 million rows
and ~70 float columns showed an overhead of ~66 seconds for doing COPY
as opposed to COPY BINARY (the actual problem report was that doing
"select * from table" from R was taking a minute+ longer than expected,
we got comparative timings for COPY just to narrow down causes).
That translates to approx. 0.00035 ms overhead (i.e. time(float8out) -
time(float8send)) per conversion (Linux server, hardware unknown).
That 66 seconds was the difference between 18s and 1m24s, so it wasn't a
small factor but totally dominated the query time.
--
Andrew (irc:RhodiumToad)
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2018-09-27 04:03:05 | Re: Let's stop with the retail rebuilds of src/port/ files already |
Previous Message | Tom Lane | 2018-09-27 03:21:35 | Re: Performance improvements for src/port/snprintf.c |