Performance optimization?

[anonymous]

Just ran into this via StackOverflow:

​https://github.com/matjaz/jquery.fly/

​http://jsperf.com/jquery-fly/4

I've no idea on the merit of the code, but an occasional x4 performance seems like an idea worth investigating...

[anonymous]

There may actually be some situations where calling the full jQuery constructor is unneccesary. This could actually be of use internally as a micro-optimisation.

[holegary@…]

Ref stackoverflow: ​http://stackoverflow.com/questions/6198633/what-is-jquery-fly-plugin-used-for

Could potentially be a reasonable performance gain when iterating over a large number of items, though could cause problems using .context, .selector, etc, although it's worth investigating where jQuery can be cached wherever reasonably possible.

[dmethvin]

I think this is a pattern to be applied externally, rather than exposed from jQuery core itself. In many $.each loops there may not be a need at all for a jQuery object and creating one unnecessarily would waste time/memory.

[dmethvin]

Went through 1.6.1 and there do seem to be some places where we can create one jQuery object outside the scope and just update the single element rather than constructing with jQuery(this). Might be worth a look.

[dmethvin]

#9525 is a duplicate of this ticket.

[shadedecho]

FWIW, I explained over on #9525 that I don't think these two are duplicates, but they are simiilar in spirit.

​http://bugs.jquery.com/ticket/9525#comment:4

[Rick Waldron]

If this is a pattern that you find useful then feel free to use it, however we feel that this is not a suitable addition to the jQuery Core.