Side navigation
#8437 closed bug (wontfix)
Opened March 03, 2011 06:26PM UTC
Closed March 30, 2011 05:16PM UTC
Last modified March 14, 2012 12:54PM UTC
Using Multiple Selectors to search by tag name is significantly slower since 1.4.3
| Reported by: | jseger@athenahealth.com | Owned by: | jseger@athenahealth.com |
|---|---|---|---|
| Priority: | undecided | Milestone: | 1.next |
| Component: | selector | Version: | 1.4.3 |
| Keywords: | Cc: | ||
| Blocked by: | Blocking: |
Description
Starting in jQuery 1.4.3, finding elements using multiple selectors and tag names is dramatically slower (10-30x slower).
For example .('input,select') now takes much longer.
See performance tests at:
Attachments (0)
Change History (3)
Changed March 07, 2011 01:42AM UTC by comment:1
| component: | unfiled → selector |
|---|---|
| owner: | → jseger@athenahealth.com |
| status: | new → pending |
Changed March 07, 2011 02:56AM UTC by comment:2
| status: | pending → new |
|---|
Interesting, it seems to perform fine in your test when searching for divs/spans, but it's still slow searching for inputs/selects.
In this version, I took your test, increased the count from 500 to 1000 (to help emphasis the slowness), and repeated all of your tests but searched from 'input,select' instead of 'div,span'.
Changed March 30, 2011 05:16PM UTC by comment:3
| resolution: | → wontfix |
|---|---|
| status: | new → closed |
In 1.4.3, Sizzle began branching as much selector work to querySelectorAll, which results in less work and overall higher performance.
I'm getting different results with a perf test that we've used on other recent dom traversal/manipulation...
http://jsperf.com/multiple-tag-selector