Whoops, looks like we both replied at the same time. On Feb 8, 2008 10:55 AM, Jim Kingdon <[EMAIL PROTECTED]> wrote: > > The newer Mayfly code appears to be causing the Mifos test suite from > > trunk revision 12291 (latest as of right now) to run about 25% slower > > Oh, man. Why couldn't you have an easy problem?
:) > > I suppose it might speed up Mayfly if it were built without debugging > > info > > Well, you can try it and see if it speeds anything up, but if Java > debugging info is anything like C debugging info, it shouldn't affect > run times (the latter isn't even faulted into memory, much less looked > at, unless debugging is going on). You're right, it didn't help. That's a relief since debugging info is a necessity, in my humble opinion. As for which part of Mayfly is slower, I'll try a few JIP tests while I still have this Mayfly/Mifos test environment set up. I don't suppose the fact that we whittled it down to LatestTest helps much in this regard since LatestTest probably uses most of the Mayfly code. -- Adam Monsen ------------------------------------------------------------------------- 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/
