Profiling resultSet.getXXX methods

Hi,

I'm working on a JDBC performance impovement project. Researching JDBC best practices it's my understanding that you should avoid getObject behavior and use type specific methods (getInt, getFloat, etc) I'm finding that in some instances that performance is worst when I use the type specific methods. Also I find that the performance results are inconsistent with either getObject or the type specific methods. It's very interesting that sometimes it takes 10 miliseconds while others are 0 milliseconds. I'm wondering if there is any signifigances to the 10 milliseconds because either I see 0 milliseconds or 10 milliseconds.

Any suggestions would be appreciated...

[696 byte] By [bob000000a] at [2007-11-27 5:00:52]
# 1

No 0 or 10 is meaningless.

At this level you are encountering limitations in the timing granularity of your OS (probably Windows).

The readings only have a granularity in 10 chunks. So zero could be anything between 0 and 9 and 10 anywhere between 11 and 19. So it could be the difference between 9 and 10 for all you know and can tell.

Which is insignificant and meaningless.

cotton.ma at 2007-7-12 10:18:00 > top of Java-index,Database Connectivity,Java Database Connectivity (JDBC)...