This test was done by modifying the DynaTable example. look up this
thread for more details "RPC still slow in IE 6"
use "gen -gen" to see the generated classes...
(loading 2000 Person objects in DynaTable)
47362ms hosted IE6/Win32
28330ms web IE6/Win32
20298ms web FF/Win32
24470ms hosted IE6
8391ms web IE6/Win32
953ms web FF/Win32
a) I'll mention you in the GWT blog if you can find a way to make IE
b) Those are my numbers. ;)
first of all here is some generated code that i have wrapped with
profiling. i have provided u guys as as much as i can b/c my results
are opposite to yours. i _must_ be doing something wrong.
here are my FF results
here are my IE6 results
you will notice that i had to drop the payload down to 40 people
objects. ff kept interupting with "continue script" messages. i wanted
to eliminate that.
the numbers at the end in parenthesis represent elapsed time since the
beginning of its associated instruction set.
based on this analysis, i would be asking why is the spotlight on ie?
pls let me know what ive done wrong.
In ClientSerializationStreamReader, set index to results.length (using
a native method to get the array length.) Then, instead of
results.pop(), always do
In my tests I serialzed 3000 DataObjects which each contained two
Strings and one unique Date.
(median of 3 test run in a succession on a 1.80 ghz pentium M)
It cuts the time by about a fifteenth. Thats a 1550% speed improvement!
Great work Sam, thanks a lot!
How would you prefer to be recognized in the blog post? We can
include your email address, or a link to your website or blog.