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

Add compiler benchmarks #103

Open
gcampax opened this issue Jul 10, 2019 · 0 comments
Open

Add compiler benchmarks #103

gcampax opened this issue Jul 10, 2019 · 0 comments
Labels
P3 Nice to have, not working on it for now performance Issues related to performance and scaling

Comments

@gcampax
Copy link
Contributor

gcampax commented Jul 10, 2019

As the ThingTalk compiler grows in complexity, we should benchmark & profile the time spent doing:

  • parsing
  • typechecking
  • compilation to JS code
  • compilation of JS code

This way, we can decide whether it is meaningful to have a compiled code cache for frequently used commands, and at what level (JS code or JS function), and whether JSIR-level optimizations (eg dead code elimination, common subexpression elimination) are meaningful, when the JS backend compiler cannot do them easily.

@gcampax gcampax added the performance Issues related to performance and scaling label Jul 10, 2019
@nrser nrser added the P3 Nice to have, not working on it for now label Aug 4, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P3 Nice to have, not working on it for now performance Issues related to performance and scaling
Projects
None yet
Development

No branches or pull requests

2 participants