>> PS >> It is a great shame that there is not a simple JUnit profiler add-on >> available which would show these >> kinds of issue straight away - any takers?. > > Yes, well, Yourkit does a good job, usually...
As a matter of fact, after a short, superficial profiling session, I can confirm that most of jOOQ's current overhead (jOOQ 3.0 latest GitHub version), originates from looking up fields / tables in HashMaps, or in other words, from hashCode calculations. In fact, field / table hashCode calculations are particularly inefficient, as they currently go through all of that schema / table mapping business. I think a quick fix for fields / tables should be possible. This could be downgraded to jOOQ 2.6.x and released before jOOQ 3.0 Cheers Lukas
