Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Acording to VS perf anylser, this reduces node.js update() from #106

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

funinvegas
Copy link
Contributor

4.6% exclusive CPU to 1.9% exclusive CPU.

Commenting out the getUid() saved another 0.5%.

This change moves transition only code into a seperate function,
and only calls it if transitions are have been used on this node.
This saves several assignments and construction of inline {} object.

4.6% exclusive CPU to 1.9% exclusive CPU.

Commenting out the getUid() saved another 0.5%.

This change moves transition only code into a seperate function,
and only calls it if transitions are have been used on this node.
This saves several assignments and construction of inline {} object.
@funinvegas
Copy link
Contributor Author

I commented out the getUID because it saved another 0.5% cpu and was initializing a variable that wasn't used later.
What are these UID's for anyways?

@bulkan
Copy link
Contributor

bulkan commented Sep 10, 2013

how do we know that these (micro) optimisations aren't breaking existing games ?

@yushli
Copy link

yushli commented Apr 26, 2014

If the data is correct, "4.6% exclusive CPU to 1.9% exclusive CPU, Commenting out the getUid() saved another 0.5%", then it is worth looking into it. Does the limejs team have any plan to do with this pull request?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants