https://github.com/chadhietala/sloshing-example

https://github.com/chadhietala/sloshing-example

Last synced: 2 months ago
JSON representation

• Host: GitHub
• URL: https://github.com/chadhietala/sloshing-example
• Owner: chadhietala
• Created: 2017-02-16T16:41:31.000Z (over 8 years ago)
• Default Branch: master
• Last Pushed: 2017-02-16T16:43:48.000Z (over 8 years ago)
• Last Synced: 2025-02-10T08:23:13.775Z (4 months ago)
• Language: JavaScript
• Size: 835 KB
• Stars: 0
• Watchers: 1
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
# sloshing-example

This example quickly shows the cost associated with not leveraging JITd code in V8. The example is pretty simple, render 200 components on the page.

## Not leveraging JITd Code

![Not Sharing Code](./not-sharing.png)

## Leveraging JITd Code (About 200ms faster)

![Sharing Code](./sharing.png)

The difference here is that in the first example we iterate 200 times, rendering a specific component for each item in the list. This means the we use the component once the VM never sees it again. However, optimized code was compiled for it, but we never use it again.

The second example uses the a single component and we just create new instances of it with different data. Because the same code is seen many times it leverages the optimized code and can even optimize further as it becomes hot.

This has nothing really to do with Ember, but more of the fact that the system you are writing against can go way faster if you work within its assumptions.

To reproduce please do `ember server --environment=production`. Then comment/uncomment out the each blocks in application.hbs.