> I had to patch build.xml to include the profile-test target Ah. Unfortunately for this approach, PerformanceTest.java isn't (yet at least) that off-the-shelf. Most of the interesting tests are commented out. The reason that Mayfly showed up in your profile at all is the setUp method.
> Looks like MayflyDialect.openConnection() might be more expensive. You're right that openConnection is near the top of that profile. But the fact that you are getting different results for the two different versions of Mayfly is probably an artifact of JIP (as noted in the comment to the blog post I pointed to). It makes method calls look more expensive than they really are. > Maybe. I have no idea. I guess I'm out of expertise and budgeted time > at this point. Well, with respect to "expertise", the lowest-skill thing which might help was the binary search on mayfly versions. With respect to time, well, isn't that the way it always is :-(. ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
