jamesplease / jamesplease/puppets

Determine most efficient rendering mechanism

Open
#13 0 comments 0 reactions 0 assignees View on GitHub
question
Dominant language
No language data
Stars
4
Forks
0
PR merge metrics
No merged PRs in 30d

Description

I thought that reducing the # of DOM operations affecting attached nodes would provide a huge speed boost, but Minionette does not do this, and preliminary tests show that my method may, in fact, be slower. [Ref](https://github.com/jmeas/dom-op-tester/pull/1)

Todo: learn more about reflows and browser performance. What causes a reflow? Why aren't those 10k DOM operations slowing anything down?

When Marionette switched to a document fragment to buffer its collection view rendering, it apparently got a big speed boost. What was the reason behind that? Is it not the same principle here?

Lots of articles on reflow mention that adding/removing nodes will always cause a reflow. And these operations are doing precisely that...so I should do more research on what's happening!

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reviewing the linked dom-op-tester pull request and the issue's questions about reflows, browser performance, and document fragments. Compare the observed rendering approaches and determine which mechanism is most efficient; done should include a supported decision based on performance findings.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
frontend, performance
Issue type
Refactor
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.