Description Mike Wilson 2001-10-11 14:23:13 EDT

PJM (8/22/2001 4:14:57 PM)
	David Whiteman did a few tests timing image related stuff between JDK 
AWT, our AWT, and 
	SWT.  
NOTES:

PJM (8/22/2001 4:17:48 PM)
	Andrew Sandstrom did some looking at AOT'ing and JIT'ing bits and 
pieces.  Here are
	the relevant notes:

        Using a pretty vanilla Smartlinker feedback  directed optimization loop 
I can get about the 
        same performance (1.8-1.9 sec) and ony 53K bigger.

        Here is what you can do.

        Run the app once with the following option:

        -Xrunslprof:fn=D:\SmartlinkerProfiling\out,of=xml,pm=cpu,sp=1,st=true

        Then add the following options to your jxeLinkOptions file:

        -cp D:\SmartlinkerProfiling\
        -feedbackProfile out
        -precompileByGain 100

        You can replace "D:\SmartlinkerProfiling" with any directory

        I tried different scenarios with running multiple times, profiling 
calls and adding 
        -inlineHotCallSites, etc, but I didn't get much benefit beyond the 
simple straightforward 
        approach.

        -Andrew

	MVM - (28/08/01 9:28:04 AM)
		We all know that AOT and JITing only helps on Win and AIX.  I 
would like to see 
		the C version personally, especially as SWT for Palm now uses 
some image loading etc.. and will not
		benefit from this, and is currently extremely slow due to this.