What are you sorting? (can you provide the test?) You could look at about:stats and see if the GC times are going nuts. Or, if you're sorting DOM nodes, it may be that we're getting bogged down with large numbers of JS wrapper creations.
Mike On Tue, Dec 16, 2008 at 12:34 PM, Andy <[email protected]> wrote: > > Hi, All > > Just did some tests about quick sort across the Chrome/Firefox/IE7. > Here is the results: > > samples: 0.3K 3K 30K > nlog(n): 743 10431 134313 > Chrome: 400 13700 1316501(only 1 time, it's around 20mins) > Firefox: 1200 28240 no-response > IE7: 2500 638406 no need to > > 30K results > Quick Sort > Times(ms) Total Avg Max > Total 1316501 348 320 > Work 42961 11 124 > Overhead 1273540 336 699 > > Env: Core2duo 2.33G, mem 4G, XP2002-SP3, Chrome 1.0.154.36 > > It seems Chrome is fast, really fast but need to improve when samples > are big, very big. > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Chromium-dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/chromium-dev?hl=en -~----------~----~----~----~------~----~------~--~---
