That's... odd. Are there any selectors that are noticeably faster? Maybe something is failing?
--John On Mon, Oct 20, 2008 at 6:07 AM, Arnar Birgisson <[EMAIL PROTECTED]> wrote: > Hi all, > >> On Tue, Aug 26, 2008 at 13:38, Chris Lee-Messer >>> 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. > > I just upgraded to FF 3.1b1 and I'm seeing this strange thing. For me, > MochiKit trunk completes in 1893ms, MochiKit w/Sizzle in 54ms but > Sizzle itself in ~100ms - no matter if it is run before or after the > MochiKit/Sizzle combo. > > So, MochiKit+Sizzle is almost twice as fast as Sizzle standalone. > > John, can you think of a good reason for this? > > cheers, > Arnar > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "MochiKit" group. To post to this group, send email to mochikit@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
