Re: Performance problem with timestamps in result sets - Mailing list pgsql-jdbc

From Thomas Dudziak
Subject Re: Performance problem with timestamps in result sets
Date
Msg-id 224f32340603081040m46f87698y49f3bbc11cfb31df@mail.gmail.com
Whole thread Raw
In response to Re: Performance problem with timestamps in result sets  (Steve Wampler <swampler@noao.edu>)
List pgsql-jdbc
Hi,

I've run the attached sample with these results (1.000.000 rows):

no profiler: 7.850ms for the int's, 58.902ms for the timestamp's

cpu profiling: 8.865ms for the int's, 60.357ms for the timestamp's

cpu profiling with method count: 262.802ms for the ints, 695.188ms for
the timestamps

 - getTimestamp(int) took 499.047ms for the  1.000.000 invocations
   with toTimestamp(Calendar, String) 378.854ms of that
   in contrast, getLong(int) took 169.703ms

It does not seem linear (the profiler definitely has some influence,
though a strange one).

Tom

Attachment

pgsql-jdbc by date:

Previous
From: Nikola Milutinovic
Date:
Subject: Re: Connection String
Next
From: Oliver Jowett
Date:
Subject: Re: Performance problem with timestamps in result sets