On 22 May 2007 12:53:37 -0400, Egor Pasko <[EMAIL PROTECTED]> wrote:
On the 0x2DE day of Apache Harmony Mikhail Fursov wrote:
> All,
> I think this is not a good idea to make JIT always work in release mode.
> I agree that STL performance we have in JIT in debug build is also almost
> unusable on Windows64bit.
> I propose learning MSVC2005 STL options and check is we can disable some
> checks and speedup the JIT.
> Here is an example of such an option:
>
http://groups.google.co.nz/group/microsoft.public.vc.stl/browse_thread/thread/24426056e5b256ea/0efe8dcc5f3ed97b?lnk=gst&q=debug+performance&rnum=2&hl=en#0efe8dcc5f3ed97b
+1 to disable thorough STL checking in w/64/debug if possible
+1
> Right now I can't test it because I run tests on my Windows64bit PC, but I
> will check this one and other options tomorrow.
>
>
> On 5/22/07, Xiao-Feng Li <[EMAIL PROTECTED]> wrote:
> >
> > Vladimir, if the testing is really slow, I think it's ok to try the
> > release build on Win64. But I personally prefer to use debug build for
> > other cases if their times are ok, because debug build can help to
> > identify the reasons of any potential breaks.
> >
> > (Or we can use release build for only the JIT module, while keeping
> > other modules in debug build.)
> >
> > Thanks,
> > xiaofeng
> >
> > On 5/22/07, Vladimir Ivanov <[EMAIL PROTECTED]> wrote:
> > > Does it means that we can use only 'release' build for testing while
> > > 'debug' build required more than 10 hours to run DRLVM tests?
> > >
> > > thanks, Vladimir
> > >
> > > On 5/18/07, Mikhail Fursov <[EMAIL PROTECTED]> wrote:
> > > > I think the numbers you mention are from debug build.
> > > >
> > > > The reason of significant compilation time increase when using Windows
> > > > x86_64 is MSVS2005 STL implementation. It does a lot of checks in
> > debug mode
> > > > that MSVS2003 version did not.
> > > >
> > > >
> > > > On 5/18/07, Vladimir Ivanov <[EMAIL PROTECTED]> wrote:
> > > > >
> > > > > Hello everyone,
> > > > > I have a small question about JIT performance on Windows x86_64: why
> > > > > the DRLVM kernel test java.lang.ClassGenericsTest, for example,
> > > > > required in my env:
> > > > > ~20 seconds to finish in the default mode;
> > > > > ~400 seconds to finish in the 'opt' mode;
> > > > > ~2000 seconds to finish in the 'server' mode.
> > > > >
> > > > > I know that this platform was only enabled but may be someone from
> > JIT
> > > > > expert spends some time to improve performance a little bit?
> > > > >
> > > > > Thanks, Vladimir
> > > > >
> > > >
> > > >
> > > >
> > > > --
> > > > Mikhail Fursov
> > > >
> > >
> >
> >
> > --
> > http://xiao-feng.blogspot.com
> >
>
>
>
> --
> Mikhail Fursov
--
Egor Pasko
--
http://xiao-feng.blogspot.com