Thanks for reply.
>This could easily be caused by something outside of the test itself.
Background processes. A monitoring system kicking in to write some data to
disk will cause a drop like this.
>Three things you could look into to try and track down the issue:
>-Did you turn on log_checkpoin
It is always better to run performance script and database on different
machines.
>From DBT5 documentation it doesn't seems like you can connect to remote
host.
If yo found you can use that.
If it is not present then:-
Use wrapper tools like pg_bench tool which samrat has suggested .
where you
