-
Notifications
You must be signed in to change notification settings - Fork 75
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
Pre-build and caching requires some more investigation #212
Comments
From a couple of different approaches that I've taken for an actual build step, nothing seems to fully stick from a Lasso build environment to the next instance of Lasso being used within the context of a runtime environment. This is all being done to Docker containers and is being tested on some Heroku-16 stack.
I've taken the following approaches:
The container will build properly, assets are generated, etc. However the first visit on a server will generate this response time spike:
These are the response spikes for both a deploy for approach 2 and 3. The first spike around 12:15 is as a user is navigating through the site with approach 2 and the spike at 12:35 is with approach 3. This isn't to say everything is doom and gloom. Once a site is up and running, the response time, even on Heroku dynos, will sit under 300ms. The only thing that I can attribute this to, is Lasso simply not getting the same information during build for the Any ideas or direction on generating a consistent .cache during build time for runtime lasso to pick up and run with? |
@austinkelleher Any update on pre-build support with 4d1d888 ? |
hey @ianvonholt I have created #299 that should help you out with your lassoPage build times. |
From @ianvonholt 12:26
The text was updated successfully, but these errors were encountered: