,
Jinhua Luo
2016-01-19 12:50 GMT+08:00 Jinhua Luo :
> Hi,
>
> I thought with async commit enabled, the backend process would rarely
> do file io. But in fact, it still involves a lot of file io.
>
> After inspecting the vfs probes using systemtap, and reading the
> source codes o
.
Regards,
Jinhua Luo
--
Sent via pgsql-performance mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance
,
1231, 'o',
'kkkkkkkkkkk');
---
The final backtrace result is converted into flame graph, see:
http://luajit.io/systemtap/pgsql/postgres_1.svg
Any advice?
Regards,
Jinhua Luo
2016-01-11 5:05 GMT+08
o',
'kkk');
pgbench -r -N -n -c 4 -j 1 -T 600 -f test.sql
I also compile and run it on the latest 9.4 version, the same issue.
Regards,
Jinhua Luo
2016-01-12 3:20 GMT+08:00 Jeff Janes :
> On Sat, Jan 9, 2016 at 9:57 PM, Jinh
does a lot of IO (vfs level), and I doubt the
duration spikes are due to the IO contention from time to time.
But I do not understand that why the process do so many IO with async
commit? And it does not even happen at the shared buffer flushing and locks
waiting. Where's the code path doing these IO?
Regards,
Jinhua Luo
