| From: | "Thomas Dudziak" <tomdzk(at)gmail(dot)com> |
|---|---|
| To: | pgsql-jdbc(at)postgresql(dot)org |
| Subject: | Re: Performance problem with timestamps in result sets |
| Date: | 2006-03-08 18:40:43 |
| Message-ID: | 224f32340603081040m46f87698y49f3bbc11cfb31df@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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 | Content-Type | Size |
|---|---|---|
| Main.java | application/octet-stream | 3.2 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Oliver Jowett | 2006-03-09 08:54:44 | Re: Performance problem with timestamps in result sets |
| Previous Message | Nikola Milutinovic | 2006-03-08 16:46:40 | Re: Connection String |