pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Matthias Meixner <meixner@dvs1.informatik.tu-darmstadt.de>
To: Rod Taylor <rbt@rbt.ca>
Cc: Mario Weilguni <mweilguni@sime.com>
Cc: Manfred Koizar <mkoi-pg@aon.at>
Cc: Postgresql Performance <pgsql-performance@postgresql.org>
Subject: Re: Write ahead logging
Date: Fri, 07 Mar 2003 09:44:22 +0100
Message-ID: <3E685BE6.4090008@dvs1.informatik.tu-darmstadt.de> (raw)
In-Reply-To: <1046993755.487.86.camel@jester>
References: <3E5494DA.20003@dvs1.informatik.tu-darmstadt.de>
	<d2795vc9bk18269rns92abumarpaukvsqm@4ax.com>
	<000b01c2d8c2$54008350$8f01c00a@icomedias.com>
	<3E55E8E0.60201@dvs1.informatik.tu-darmstadt.de>
	<1046993755.487.86.camel@jester>

Rod Taylor wrote:
> What were you using to measure the latency.  Don't suppose you could
> send it over.  The admins locally don't like what I used to do the test
> with -- they don't want to turn off write-caching for other reasons.

I am doing an insert of few bytes, so that the amount of data does not
significantly affect the measured time. And for measuring time without
cache, I temporarily switched it off.

That was the code used (nothing unusual):

#include "timeval.h"

main()
{
     Timeval start,end;
EXEC SQL WHENEVER sqlerror sqlprint;
EXEC SQL WHENEVER not found sqlprint;

EXEC SQL CONNECT TO user@localhost;
     start=Timeval::Time();
EXEC SQL BEGIN;
EXEC SQL INSERT INTO test values ('qwertz');
EXEC SQL COMMIT;
     end=Timeval::Time();
     end-=start;
     printf("time: %d.%06d\n",end.tv_sec,end.tv_usec);
}


- Matthias Meixner

-- 
Matthias Meixner                       meixner@informatik.tu-darmstadt.de
Technische Universität Darmstadt
Datenbanken und Verteilte Systeme              Telefon (+49) 6151 16 6232
Wilhelminenstraße 7, D-64283 Darmstadt, Germany    Fax (+49) 6151 16 6229




view thread (6+ messages)

Message-ID: <3E685BE6.4090008@dvs1.informatik.tu-darmstadt.de>
Permalink:  ../3E685BE6.4090008@dvs1.informatik.tu-darmstadt.de/
Also on:    postgresql.org/message-id/3E685BE6.4090008@dvs1.informatik.tu-darmstadt.de

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-performance@postgresql.org
  Cc: meixner@dvs1.informatik.tu-darmstadt.de, rbt@rbt.ca, mweilguni@sime.com, mkoi-pg@aon.at
  Subject: Re: Write ahead logging
  In-Reply-To: <3E685BE6.4090008@dvs1.informatik.tu-darmstadt.de>
  References: <3E5494DA.20003@dvs1.informatik.tu-darmstadt.de> <d2795vc9bk18269rns92abumarpaukvsqm@4ax.com> <000b01c2d8c2$54008350$8f01c00a@icomedias.com> <3E55E8E0.60201@dvs1.informatik.tu-darmstadt.de> <1046993755.487.86.camel@jester> <3E685BE6.4090008@dvs1.informatik.tu-darmstadt.de>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox