LMD stats and code coverage analiser #25

azproduction opened this Issue Jun 11, 2012 · 0 comments

1 participant


The goal: optimize resource loading and initializing.

It should help with questions:

  1. What in-package files are not so often require()s? (move them from package)
  2. What off-package files are often require()s at the startup time or near that time? (make them in-package)
  3. What lazy modules are require()s on startup? (make them not lazy)
  4. What no-lazy modules are require()s while working? (make them lazy)
  5. Heavy modules detection (split into parts)
  6. Code of module is partly used (split code into parts)
@azproduction azproduction added a commit that closed this issue Jun 22, 2012
@azproduction fixes #25, fixes #26, fixes #27, fixes #28 - Code coverage, Stats ser…
…ver, async plain modules
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment