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

Source maps performance #1602

Closed
guybedford opened this issue Dec 19, 2014 · 2 comments
Closed

Source maps performance #1602

guybedford opened this issue Dec 19, 2014 · 2 comments

Comments

@guybedford
Copy link
Contributor

Traceur has been incredibly quick to parse and write large trees for SystemJS builder. Recently we added source maps support for the full bundling process and this has made compile times about 10x slower, which in some cases has driven builds from under 1 second to close to 10.

We're looking to see how we can improve performance around this, any ideas for where would be best to look here would be much appreciated.

@arv
Copy link
Collaborator

arv commented Dec 19, 2014

Maybe this is another case where we are using indexing into a string rope? Maybe a benchmark would show the problem?

@guybedford
Copy link
Contributor Author

Sounds like a sensible first step, aiming to get something together next week with some luck.

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

No branches or pull requests

2 participants