rewrite speed framework based off of the latest sizzle speed tests

[mikesherov]

have it test against an earlier build

[timmywil]

I'm not sure sizzle speed tests are the best starting point. They are specially manufactured to work with selector engines, testing each selector and each engine in their own iframes. What we need is probably something custom manufactured to test jQuery modules. Having said that, there a couple principles I think we should adopt from Sizzle's speed suite.

1. Tests don't really need a back-end. Slickspeed operates only with PHP. I don't think we even need node.
2. The benchmarkjs project is a now a submodule of Sizzle; we can update to released versions whenever we need (which shouldn't happen that often).
3. Tests should be encapsulated appropriately to guarantee that one test does not affect the other. Loading each test in its own iframe is probably going overboard in the core module, but may be right for the ajax module.

Finally, rwaldron seemed excited about revamping an old resig project for our speed tests. I'm still open to that.

[mikesherov]

I'm fine either way. I really just want to blast away the /speed dir. If Rick's on that, even better :-)

[dmethvin]

Salvatore Iovene from Intel is going to take a shot at this. If you have thoughts post here or ping siovene in #jquery-dev.

[m_gol]

dmethvin: any info on the progress on this?

[m_gol]

Migrated to ​https://github.com/jquery/jquery/issues/1737