Bug Tracker

Ticket #10426 (closed feature: notabug)

Opened 4 years ago

Last modified 2 years ago

Meta: Use createContextualFragment to speed up element creation

Reported by: rwaldron Owned by: rwaldron
Priority: low Milestone: 1.next
Component: manipulation Version: 1.7b1
Keywords: Cc:
Blocking: Blocked by:


Recently, Yehuda Katz presented this idea to both us and then the entire jQuery Boston Conference. I think it's worth (at very least) an exploratory implementation to measure performance against.

I'm going to suggest that we work on this between now and 1.8 release

Change History

comment:1 Changed 4 years ago by rwaldron

  • Owner set to rwaldron
  • Priority changed from undecided to low
  • Status changed from new to assigned
  • Component changed from unfiled to manipulation
  • Milestone changed from None to 1.8

comment:2 Changed 3 years ago by dmethvin

These kind of tickets are pretty ethereal; similar to #10515.

If we can do something here, great, if not let's close it and it will come up organically when someone yells at us for being stupid and not using them.

I am not convinced the fragment cache complexity is worthwhile, perhaps it could be swapped out for code that used cCF or iAH. The primary benefit of the frag cache is that it made us look really good on benchmarks like TaskSpeed circa 2008, but anyone writing production code like that deserves to have bad performance.

comment:3 Changed 3 years ago by mikesherov

  • Milestone changed from 1.8 to 1.next

comment:4 Changed 3 years ago by dmethvin

  • Type changed from enhancement to feature

Bulk change from enhancement to feature.

comment:5 Changed 2 years ago by dmethvin

  • Status changed from assigned to closed
  • Resolution set to notabug

I'll take my advice above and close this until someone shows it really helps. Based on the work orkel did on #10515 I have my doubts.

Note: See TracTickets for help on using tickets.