Adding Sizzle sounds like a substantial plus, I noticed that your addition fixes the errors in MochiKit.Selector. Does it break any of the other (non-selector related) tests in MochiKit?
-Chris p.s. I'm running firefox 3.1pre now with the JIT running, and slickspeed tests are interesting as your version of MochiKit.Selector is reported as faster than Sizzle: most of the response times are 1ms for a total time of 45ms vs 174ms for Sizzle itself. I would guess that some compiled code is being cached. MochiKit's current Selector comes in with a time of 4045ms. On Aug 25, 9:11 am, "Arnar Birgisson" <[EMAIL PROTECTED]> wrote: > Hi again, > > On Mon, Aug 25, 2008 at 16:06, Arnar Birgisson <[EMAIL PROTECTED]> wrote: > > For this benchmark, regular MochiKit completed all tests in 3983 > > milliseconds. The MochiKit+Sizzle combination does it in 61. That > > means we are talking about a speedup by a factor of roughly 65! > > Sorry, forgot to mention that this is running on my computer on > Firefox 3.0. For browsers that support the querySelectorAll method > (such as FF 3.1), I'd expect an even greater speedup. > > cheers, > Arnar --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "MochiKit" 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/mochikit?hl=en -~----------~----~----~----~------~----~------~--~---
