You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently tracking bottle-necks in code compilation is pretty much impossible (especially for improving compilation time by reducing e.g. implicits or macros usage).
What we want is tool to tracking amount of time spend on compiling given node in AST (at best). We are aware that it can be almost impossible for multiple reason:
To much information to track - we can also live with method or even class level information
Impossible to assign time to given place in AST (e.g. cycle dependencies) - this time can be logged (if possible) as "other"
I know could not be accurate but this should be better then nothing. I think current counters/trimmers should be suitable for this.
The text was updated successfully, but these errors were encountered:
Currently tracking bottle-necks in code compilation is pretty much impossible (especially for improving compilation time by reducing e.g. implicits or macros usage).
What we want is tool to tracking amount of time spend on compiling given node in AST (at best). We are aware that it can be almost impossible for multiple reason:
I know could not be accurate but this should be better then nothing. I think current counters/trimmers should be suitable for this.
The text was updated successfully, but these errors were encountered: