Oh hello, incremental builds!
@eleven_ty now takes ~1.5 to rebuild the ~1300 page site.
Netlify Build Plugins makes build cache available!
👉 https://www.netlify.com/build/plugins-beta?utm_source=twitter&utm_medium=plugins-incremental-pnh&utm_campaign=devex
And wow! @eleven_ty's pagination has some nifty tricks to help make the pages!
👉 https://www.11ty.dev/docs/pagination/#the-before-callback
@bzmills @wesbos @stolinski @syntaxfm @Netlify Nice!
I tried to illustrate how to use that in this blog post. I'd love to hear more about your implementation!
https://www.netlify.com/blog/2020/03/19/learn-how-to-add-jamstack-to-your-infrastructure-in-8-minutes/
I tried to illustrate how to use that in this blog post. I'd love to hear more about your implementation!
https://www.netlify.com/blog/2020/03/19/learn-how-to-add-jamstack-to-your-infrastructure-in-8-minutes/
@zachleat @nhoizey @hankchizljaw @eleven_ty @Netlify Any thoughts on what you'll be using that time for now that you're getting it back?
RT @jlengstorf: 🔴 live now!
I’m doing a solo stream to build a @Netlify Build Plugin
come learn about the powerful customizations this un…
I’m doing a solo stream to build a @Netlify Build Plugin
come learn about the powerful customizations this un…
@iambolajiayo @DThompsonDev @techgirl1908 @dabit3 @sarah_edo @EmmaBostian @TatianaTMac @TaelurAlexis @Zfinix1 @AdoraNwodo @lauragift_ @TejasKumar_ @tlakomy @unicodeveloper @Ace_KYD @cassidoo @yomdroid @VishwaMehta30 @iamdillion @jamesqquick @kentcdodds How very flattering! 🤗
@polarbirke @hankchizljaw @eleven_ty @Netlify Ha! It's a tough competition where we all win because the web gets faster.
(And also, these are build times for the entire 1200 page site, not client-side page render times. The build does the work, so your browser won't have to)
(And also, these are build times for the entire 1200 page site, not client-side page render times. The build does the work, so your browser won't have to)
@donebysimon @eleven_ty @Netlify @devinekask @contentful @gatsbyjs @wesbos I'd be curious to hear of any concepts or techniques around Jamstack which people found confusing/interesting/valuable/challenging.
@hankchizljaw @eleven_ty @Netlify I've had about 10 more deploys since I upgraded to the @eleven_ty v0.10.0, and the average is around 6.8 seconds to generate those ~1200 (+10 now 😉) pages.
So if anything, it's a tiny bit slower. But the sample is too small and too narrow to be sure.
I could optimise my bits
So if anything, it's a tiny bit slower. But the sample is too small and too narrow to be sure.
I could optimise my bits
@hankchizljaw @eleven_ty @Netlify You convinced me.
Ok, I'll bump the version, test locally, and deploy it.
Then we can see how it compares in the Netlify Build infra.
Ok, I'll bump the version, test locally, and deploy it.
Then we can see how it compares in the Netlify Build infra.
@chrisbiscardi @eleven_ty @Netlify I've done nothing to optimise anything here in the build really. That Netlify time will be bootstrapping the build environment, restoring cached dependencies, running the build, packing the serverless functions and deploying to AWS, and the updating the caching in our global CDN
@hankchizljaw @eleven_ty @Netlify I should upgrade @eleven_ty from v0.8.3 to v0.10 to see if it gets any sort of site generation speed bump. (Although I'm happy with this, and new pages are available instantly due to the serverless rendering as a fallback)
Happy to see this little demo still chugging away making lollipops for people.
🍭 https://vlolly.net
@eleven_ty takes ~ 6.5 seconds to generate almost 1200 pages.
@Netlify takes ~ 51 seconds to build and deploy the site and the serverless API
? 👉 https://css-tricks.com/static-first-pre-generated-jamstack-sites-with-serverless-rendering-as-a-fallback/
🍭 https://vlolly.net
@eleven_ty takes ~ 6.5 seconds to generate almost 1200 pages.
@Netlify takes ~ 51 seconds to build and deploy the site and the serverless API
? 👉 https://css-tricks.com/static-first-pre-generated-jamstack-sites-with-serverless-rendering-as-a-fallback/