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
It would be cool if we could tell the tasks to run in interpreted mode instead of waiting to compile. For larger apps, compile time on these tasks can get to be a bit much. (i.e. 90+ seconds before execution starts).
As of this writing, the Crystal interpreter is still in development and requires building a custom Crystal binary with it enabled. Until it's native, this won't be available as a default option, but we could potentially make it also behind a flag.
I have no clue how the performance would be, but I'm hoping that there may be cases where running slower code in the interpreter would be the optimal choice because maybe the code won't take long to run anyway, and time to first execution would be a lot faster than waiting on the compiler.
The text was updated successfully, but these errors were encountered:
It would be cool if we could tell the tasks to run in interpreted mode instead of waiting to compile. For larger apps, compile time on these tasks can get to be a bit much. (i.e. 90+ seconds before execution starts).
As of this writing, the Crystal interpreter is still in development and requires building a custom Crystal binary with it enabled. Until it's native, this won't be available as a default option, but we could potentially make it also behind a flag.
I have no clue how the performance would be, but I'm hoping that there may be cases where running slower code in the interpreter would be the optimal choice because maybe the code won't take long to run anyway, and time to first execution would be a lot faster than waiting on the compiler.
The text was updated successfully, but these errors were encountered: